dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-42476

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
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.

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 confidence

The OAuth library for Nim uses plain `assert` statements to validate the `state` parameter in Authorization Code and Implicit grant flows, which prevents CSRF attacks. When compiled with `-d:danger` or `--assertions:off` flags, these assertions are completely removed, disabling CSRF protection and allowing attackers to bind victim sessions to attacker-controlled OAuth states.

MitigationUpgrade the OAuth library to version 0.11 or later, which uses `doAssert` or `if` statements that remain active regardless of compiler flags. Alternatively, ensure the library is never compiled with dangerous optimization flags.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OAuth library version
    Check your project's dependency file (e.g., nimble, nimble.lock, or package.json equivalent) for the oauth library version, or run 'nimble path oauth' to locate the library and check its nimble file for version number
    Affected if version is 0.10 or earlier and the library is used for Authorization Code or Implicit grant flows
  2. Check compiler flags used in build
    Review your build pipeline, Makefile, Nimble configuration, or compilation scripts for the presence of '-d:danger' or '--assertions:off' flags
    Affected if either flag is present in the compilation command used to build the application
  3. Inspect source code for assert usage
    Locate the OAuth library source code (typically in your nimble packages directory) and examine the code handling the 'state' parameter in authorization code and implicit grant flows; search for plain 'assert' statements validating state
    Affected if the code uses plain 'assert' statements (not 'doAssert' or 'if' conditionals) for state parameter validation and the library is compiled with assertions disabled

You are affected if your Nim OAuth library version is 0.10 or earlier AND your application is compiled with -d:danger or --assertions:off flags, or if the library source still uses plain assert for state validation in OAuth flows.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the OAuth library to version 0.11 or later, which uses `doAssert` or `if` statements that remain active regardless of compiler flags. Alternatively, ensure the library is never compiled with dangerous optimization flags.

Recommended fix High confidence

0.11

  1. Upgrade the OAuth library for Nim to version 0.11 or later
  2. Verify that the `state` parameter validation is being performed correctly in your OAuth implementation
  3. If using custom compilation flags like `-d:danger` or `--assertions:off`, ensure the OAuth flow still validates the state parameter as expected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42476 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42476 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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