# CVE-2024-42476: oauth CSRF vulnerability

> Attackers can bypass CSRF protection in the Nim OAuth library when compiled with specific flags, potentially linking victim 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:** 20 Aug 2024
- **Also known as:** GHSA-pc9j-53g7-5x54

## What is CVE-2024-42476?

CVE-2024-42476 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 Authorization Code grant and Implicit grant both rely on the `state` parameter to prevent cross-site request forgery (CSRF) attacks where a resource owner might have their session associated with protected resources belonging to an attacker. When this project is compiled with certain compiler flags set, it is possible that the `state` parameter will not be checked at all, creating a CSRF vulnerability. Version 0.11 checks the `state` parameter using a regular `if` statement or `doAssert` instead of relying on a plain `assert`. `doAssert` will achieve the desired behavior even if `-d:danger` or `--assertions:off` is set.

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

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


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

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

## Is CVE-2024-42476 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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