Description
Here is a description of the task (translated from Spanish):
To use the exercise you must use the wackopicko application . You can find this application in the virtual machine of http://www.vulnerablewebapps.org/ , which you must download and install on your computer.
Then try to solve what is asked next:
1. Identifies all vulnerabilities in the application (you can use a semi-automatic tool).
As a result of this exercise will show on the one hand the number of occurrences identified and classified according to their level and on the other the classification of all these occurrences in typologies of vulnerabilities.
2.Exploit vulnerabilities.
As a result of this exercise you indicate with which tool the vulnerability has been exploited and what has been the result (you can attach screenshots).
3. Finally you must propose prevention measures for each vulnerability analyzed (preventive measures are all those modifications in the code that are poorly implemented). Additional measures on good safety practices in general may also be indicated.
Important:
All steps must be correctly explained, adding evidence (semiautomatic tool result report, screenshots, etc.).
Explanation & Answer
Hello buddyThe work is readyKindly check and lemme know in case of any concernCheers
Insert surname1
Professor’s name
Student’s name
Course title
Date
Identifying, Exploiting and Prevention Measures of Vulnerabilities
Introduction
The WackoPicko login form contains reflected SQL boosters in the user's name. By
applying a tick in the user's number, it can arbitrarily query and obtain data in the database, for
example, WackoPicko has been developed as a real web application with the usernames and
passwords for all users of the system. When any users want to use this form, the users need to
follow some initial stage like login process. Then comes authentication process as WackoPicko
provides his registered users with personalized contents. Uploading pictures in WackoPicko as
another user can post their views on it. All WackoPicko registered users can comment on the
recently uploaded photo after filling out the given form. They can also purchase high-quality
pictures which are uploaded in WackoPicko. The "Search" feature in WackoPicko offers his users
to filter any images by looking for the strings in the tags on the pictures. The WackoPicko
Guestbook page provides his registered users to give their feedback easily. WackoPicko also has
an area for his administrators to operate the application. It helps the new users to use the form.
This article describes all these vulnerabilities and how to protect and detect them in WackoPicko.
Insert surname2
1. Identifies all vulnerabilities in the application
WackoPickoapplication has been misdescribed by the description and classification.
Reflected XSS: In the search form, the inquiry parameters are unclear.
Stored XSS: The remark field is risky for a persistent XSS attack.
Session ID vulnerability: The session cookie rate used for administrative authentication is based
on a feeble and guessable operation (auto-incremental value).
Stored SQL Injection: The primary name field of the form of registered users contains a stored
SQL booster which is at that point used on the parallel users’ page.
Reflected SQL Injection: This username field is vulnerable.
Directory Traversal: The label field has a manual traversal vulnerability allowing any malicious
users to overwrite any file on the web server where users have access.
Multi-Step Stored XSS: The comment arena is defenseless to XSS. However one must go through
an opening form.
Forceful Browsing: Any user in this Application doesn't have the right to purchase the picture to
see the high-quality images.
Command-line Injection: The password field is defenseless to the command line injections.
File Inclusion: The /admin/index.php page is vulnerable to any file inclusion vulnerability.
However, one must include %00 at the end.
Parameter Manipulation: The user id restriction can be influenced to see any user's page in
WackoPicko when one needs to be logged in or else.
Insert surname3
Reflected XSS Behind JavaScript: The name restriction is vulnerable.
Logic Flaw: A token can be used multiple times dropping the value of an edict to zero. The
emblem in the primary data is SUPERYOU21.
Reflected XSS Behind a Flash Form: The value restriction is vulnerable.
Weak username or password: There is some default username/password amalgamation of
admin/admin.
2. Exploit vulnerabilities
1) Reflected XSSThe search page has an XSS vulnerability, which is manageable without logging in to the
application.Query parameter is not disinfected befo...
