# CVE-2018-20595: Cross-Site Request Forgery (CSRF) in hswebframework.web:hsweb-commons

> Attackers can perform CSRF attacks in hsweb by bypassing OAuth2 state validation, potentially leading to account takeover.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4rm3-4mq4-mfwr

## What is CVE-2018-20595?

CVE-2018-20595 is a high-severity vulnerability in n/a, published on 30 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-20595?

2 open source packages ship an affected version, including org.hswebframework.web:hsweb-commons. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.hswebframework.web:hsweb-commons` | Maven | All versions to 3.0.4 | None |
| `org.hswebframework.web:hsweb-commons` | Maven | All versions to 3.0.4 | None |

Products: Hsweb Hsweb.

## How do I fix CVE-2018-20595?

No fix has been published for CVE-2018-20595 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-20595 being exploited?

There is no known exploitation of CVE-2018-20595 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-20594](https://insights.sbomify.com/CVE-2018-20594/): Moderate severity vulnerability that affects org.hswebframework.web:hsweb-commons (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20595 and fix it if it is affected.

What it is: CVE-2018-20595 is a high-severity vulnerability in n/a, published on 30 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-20595 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.hswebframework.web:hsweb-commons (Maven): affected all versions up to 3.0.4; no fix listed
- org.hswebframework.web:hsweb-commons (Maven): affected all versions up to 3.0.4; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-20595/ (Markdown: https://insights.sbomify.com/CVE-2018-20595/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-20595
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-20595
- OSV: https://osv.dev/vulnerability/CVE-2018-20595

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-20595/
Summaries are generated and may contain mistakes; the official description above is the record.