CVE-2018-20595

Public Exploit

Description

A CSRF issue was discovered in web/authorization/oauth2/controller/OAuth2ClientController.java in hsweb 3.0.4 because the state parameter in the request is not compared with the state parameter in the session after user authentication is successful.

Category

8.8
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.08%
Third-Party Advisory github.com Third-Party Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/hs-web/hsweb-framework/commit/40929e9b0d336a26281a5ed2e0e721d54dd8d2f2 third party advisory patch
https://github.com/hs-web/hsweb-framework/issues/107 third party advisory issue tracking exploit

Frequently Asked Questions

What is the severity of CVE-2018-20595?
CVE-2018-20595 has been scored as a high severity vulnerability.
How to fix CVE-2018-20595?
To fix CVE-2018-20595, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-20595 being actively exploited in the wild?
It is possible that CVE-2018-20595 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.