# CVE-2024-42475: Cross-site request forgery in oauth

> Attackers can guess low-entropy OAuth state values to perform CSRF attacks, linking user sessions to attacker resources.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 15 Aug 2024
- **Updated:** 19 Aug 2024
- **Also known as:** GHSA-332c-q46h-fg8f

## What is CVE-2024-42475?

CVE-2024-42475 is a medium-severity vulnerability in CORDEA oauth, published on 15 Aug 2024. 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

In the OAuth library for nim prior to version 0.11, the `state` values generated by the `generateState` function do not have sufficient entropy. These can be successfully guessed by an attacker allowing them to perform a CSRF vs a user, associating the user's session with the attacker's protected resources. While `state` isn't exactly a cryptographic value, it should be generated in a cryptographically secure way. `generateState` should be using a CSPRNG. Version 0.11 modifies the `generateState` function to generate `state` values of at least 128 bits of entropy while using a CSPRNG.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2024-42475?


## How do I fix CVE-2024-42475?

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

## Is CVE-2024-42475 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42475 and fix it if it is affected.

What it is: CVE-2024-42475 is a medium-severity vulnerability in CORDEA oauth, published on 15 Aug 2024. 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-2024-42475 in the wild and no public exploit code.

Affected product: CORDEA oauth. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-42475/ (Markdown: https://insights.sbomify.com/CVE-2024-42475/index.md)
```

## Sources

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

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