Test Portal: Vulnerability Assessment & Penetration Testing

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 12

Test PORTAL

Vulnerability Assessment & Penetration Testing


Report

Prepared By:
Table of Contents

Number of Vulnerabilities: 2
Vulnerabilities 3
1. Session Hijacking 3
2. CSRF4
3. Click Jacking 5
4. Access Control-Allow Method 6
5. Internal Information Revealed 7
6. Insecure Transport 8
7. Token In-authentication 9
8. Exception Handling 10

Page 1
Number of Vulnerabilities:
There are 8 vulnerabilities found in test Portal. Vulnerabilities includes [1] Critical, [6] High and [1]
Medium vulnerabilities.

3 6

1
1 1
0
0

Page 2
Vulnerabilities
1. Session Hijacking

Name: Session Hijacking Severity: Critical

Description: Session hijacking includes in-authentication of session id.

Remedy: To fix this vulnerability, an attribute needs to be set, which could be done just by adding
httponly in your set_cookie http response header.

POC: Attach Pic

Page 3
2. CSRF
Name: Cross-Site Request Forgery Severity: High

Description: Cross-Site Request Forgery (CSRF) allows unauthorized commands from a user that the web
application trusts.

Remedy: Remediation factor for avoiding CSRF vulnerability includes synchronizer token patter,
disclosure of token in url, encryption based token pattern.

POC:

Page 4
3. Click Jacking
Name: Click Jacking Severity: High

Description: Clickjacking allows the attacker to trick the user into clicking on button or link, which
eventually allows attacker to hijack user’s clicks and keystrokes.

Remedy: To avoid clickjacking, send the proper content security policy frame-ancestors directive
response headers that instruct the browser to not allow framing from other domains, and employing
defensive code in the UI to ensure that the current frame is the most top level window.

POC:

Page 5
4. Access Control-Allow Method
Name: Access Control-Allow Method Severity: High

Description: Access control-allow method is a response header used by the server to describe the
methods the clients are allowed to use.

Remedy: Disable all the access control allow-methods except GET and POST.

POC:

Page 6
5. Internal Information Revealed
Name: Internal Information Revealed Severity: High

Description: Backend server and framework information are revealing.

Remedy: Backend server and framework information shouldn’t be revealing/hard-coded as they could
lead the attacker to the known possible attacks by getting the versions of those technologies.

POC:

Page 7
6. Insecure Transport
Name: Insecure Transport Severity: High

Description: Insecure communication leads to credentials transfer in plain text.

Remedy: SSL certificate needs to be installed.

POC:

Page 8
7. Token In-authentication
Name: Token In-authentication Severity: High

Description: Token in-authentication means there is no authentication of Tokens.

Remedy: Token needs to be authenticated such as that their combination with session id should allow
the user to get right response for the required request.

POC:

Page 9
8. Exception Handling
Name: Improper Error Handling Severity: Medium

Description: Exceptions are not handled properly revealing internal information.

Remedy: Proper error/exception should be thrown in response of wrong query.

POC:

Page
10
Page
11

You might also like