CVE-2024-42475
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe OAuth library for Nim prior to version 0.11 generates insufficiently entropic state values in the `generateState` function, allowing attackers to successfully guess state parameters and perform CSRF attacks by associating a user's session with the attacker's protected resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Nim OAuth library usageSearch project dependencies (nimble file, .nimble imports, or package manager listings) for 'oauth' or 'nim-oauth' packagesAffected if The Nim OAuth library is not present in dependencies
-
Determine installed OAuth library versionCheck the version field in the project's .nimble file, or run 'nimble list --installed' to see installed package versionsAffected if Version is below 0.11 (e.g., 0.10.x, 0.9.x, or any version prior to 0.11)
-
Verify OAuth state parameter usageSearch codebase for calls to 'generateState', 'state' parameter in OAuth flows, or authorization URL construction involving stateAffected if The application uses the state parameter in OAuth authorization requests but the library version is vulnerable
-
Confirm library version directlyInspect the actual oauth library source code (typically in ~/.nimble/pkgs/ or project vendor directory) and check the version identifier in the package definitionAffected if The library version file shows a version number less than 0.11
You are affected if your project uses the Nim OAuth library with version lower than 0.11 and performs OAuth authorization flows that rely on the state parameter for CSRF protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate to version 0.11 or later of the Nim OAuth library, which implements cryptographically secure state generation using a CSPRNG with at least 128 bits of entropy.
OAuth library for nim version 0.11
- Upgrade the OAuth library for nim to version 0.11 or later
- Verify that the `generateState` function is now using a CSPRNG with at least 128 bits of entropy
- Test that OAuth state validation still functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-42475 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data