dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-11705

CRITICAL · 9.1 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 133.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
`NSC_DeriveKey` inadvertently assumed that the `phKey` parameter is always non-NULL. When it was passed as NULL, a segmentation fault (SEGV) occurred, leading to crashes. This behavior conflicted with the PKCS#11 v3.0 specification, which allows `phKey` to be NULL for certain mechanisms. This vulnerability affects Firefox < 133 and Thunderbird < 133.

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 NSC_DeriveKey function in Firefox/Thunderbird's NSS library contains a NULL pointer dereference vulnerability. The function fails to validate the phKey parameter before dereferencing it, causing a segmentation fault when phKey is NULL. This violates PKCS#11 v3.0 specification which permits NULL for certain key derivation mechanisms, allowing attackers to crash the application via crafted cryptographic operations.

MitigationUpgrade to Firefox 133 or Thunderbird 133 or later to obtain the patched NSS library that properly validates the phKey parameter before use.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FirefoxWeb browser
Affected:< 133.0
ThunderbirdApplication
Affected:< 133.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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. Check Firefox version
    Open Firefox, go to Help > About Firefox, or run 'firefox --version' from command line
    Affected if Version displayed is less than 133.0 (for example 132.x, 132.0.x, or earlier)
  2. Check Thunderbird version
    Open Thunderbird, go to Help > About Thunderbird, or run 'thunderbird --version' from command line
    Affected if Version displayed is less than 133.0 (for example 132.x, 132.0.x, or earlier)
  3. Verify NSS library version if available
    Run 'grep -i nss' on the application's library dependencies or check about:support in Firefox for NSS version
    Affected if The bundled NSS library version corresponds to an unpatched release (NSS versions prior to the fix included in Firefox/Thunderbird 133.0)

You are affected if either Mozilla Firefox or Thunderbird installed on this system is version 132.x or earlier.

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
Upgrade available Upgrade to 133.0 or later
Fixed in 133.0
Interim mitigation

Upgrade to Firefox 133 or Thunderbird 133 or later to obtain the patched NSS library that properly validates the phKey parameter before use.

Recommended fix High confidence

Firefox 133.0 and Thunderbird 133.0

  1. 1. Open Firefox or Thunderbird application
  2. 2. Navigate to the Help menu (Firefox: Help > About Firefox; Thunderbird: Help > About Thunderbird)
  3. 3. The application will automatically check for updates
  4. 4. If an update is available, click 'Update' or allow the application to download and install version 133.0 or later
  5. 5. Restart the application after the update completes
  6. 6. Alternatively, download Firefox 133.0 or later from the official Mozilla website (www.mozilla.org) and Thunderbird 133.0 or later from the official Mozilla website
  7. 7. Close all instances of the browser/email client before installing the new version
  8. 8. Run the installer and follow the prompts to complete the upgrade

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing8.0 h
  • Review / QA4.0 h
15.0 hours of engineering $2,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11705 — 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-11705 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