Showing results for 
Show  only  | Search instead for 
Did you mean: 

Who Me Too'd this topic

Found VAPT vulnerabilities points for SSLVPN URL.

L2 Linker

We have done the VAPT on our environment and found the vulnerabilities for the SSLVPN URL which we use.


We had mitigated the maximum points but five points are remaining. So need help on that.




1. Password sent in Clear Text - CWE-319.

Some applications transmit passwords over unencrypted connections, making them vulnerable to interception. To exploit this vulnerability, an attacker must be suitably positioned to eavesdrop on the victim's network traffic. This scenario typically occurs when a client communicates with the server over an insecure connection such as public Wi-Fi, or a corporate or home network that is shared with a compromised computer.


2. Forced Browsing - CWE-285.

It was observed that The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.


3. Absence of CSRF tokens.

No Anti-CSRF tokens were found in a HTML submission form.
A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.


4.No logout option - CWE-613.

It was observed that the target web application has no logout option.


5.Referrer-Policy Header is not implemented - CWE-200

It was observed that Referrer-policy is not implemented in the response header.
Referrer-Policy is a security header designed to prevent cross-domain referrer leakage.



Thanks In advance,





Thanks and Regards,
Who Me Too'd this topic