Use-case :
How to perform online - Website Vulnerability Scanner Report
Solution :
- Go to this URL: https://pentest-tools.com/home
- Input the website URL https://www.test.com/ under the webserver scan tab
- Click on scan , it will generate the report and it will have various scanning parameters.
| Testing areas | Light scan | Full scan |
| Website fingerprinting | ||
| Version-based vulnerability detection | ||
| Common configuration issues | ||
| SQL injection | ||
| Cross-Site Scripting | ||
| Remote command execution | ||
| Discover sensitive files |
Summary of sample scan report
Overall risk level:
Medium
Risk ratings:
Scan information:
| Start time: | 2019-03-29 08:03:21 |
| Finish time: | 2019-03-29 08:03:28 |
| Scan duration: | 7 sec |
| Tests performed: | 10/10 |
| Scan status: | Finished |
Scan coverage information
List of tests performed (10/10)
- Fingerprinting the server software and technology...
- Checking for vulnerabilities of server-side software...
- Analyzing the security of HTTP cookies...
- Analyzing HTTP security headers...
- Checking for secure communication...
- Checking robots.txt file...
- Checking client access policies...
- Checking for directory listing (quick scan)...
- Checking for password auto-complete (quick scan)...
- Checking for clear-text submission of passwords (quick scan)...
- Server software and technology found
| Software / Version | Category |
 Apache | Web Servers |
 Adobe Experience Manager | CMS |
 ZURB Foundation | Web Frameworks |
 Google Maps | Maps |
 Google Tag Manager | Tag Managers |
 jQuery | JavaScript Frameworks |
Risk description:
Since the
Lack of the
Recommendation:
We recommend reconfiguring the web server in order to set the flag(s)
More information about this issue:
https://blog.dareboost.com/en/2016/12/secure-cookies-secure-httponly-flags/.
Since the
Secure flag is not set on the cookie, the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. Thus, the risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.Lack of the
HttpOnly flag permits the browser to access the cookie from client-side scripts (ex. JavaScript, VBScript, etc). This can be exploited by an attacker in conjuction with a Cross-Site Scripting (XSS) attack in order to steal the affected cookie. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session. Recommendation:
We recommend reconfiguring the web server in order to set the flag(s)
Secure, HttpOnly to all sensitive cookies. More information about this issue:
https://blog.dareboost.com/en/2016/12/secure-cookies-secure-httponly-flags/.
4. That's all!