dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-11704

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 128.7.0 / 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
A double-free issue could have occurred in `sec_pkcs7_decoder_start_decrypt()` when handling an error path. Under specific conditions, the same symmetric key could have been freed twice, potentially leading to memory corruption. This vulnerability affects Firefox < 133, Thunderbird < 133, Firefox ESR < 128.7, and Thunderbird < 128.7.

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

A double-free vulnerability exists in the sec_pkcs7_decoder_start_decrypt() function within Mozilla's NSS library. When handling an error path, the same symmetric encryption key can be freed twice due to improper error handling, leading to memory corruption and potential arbitrary code execution.

MitigationUpgrade to Firefox 133, Thunderbird 133, Firefox ESR 128.7, Thunderbird 128.7 or later versions to apply the security patch.

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:< 128.7.0< 133.0
ThunderbirdApplication
Affected:< 128.7.0>= 129.0, < 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
    Navigate to Firefox menu > Help > About Firefox (or enter 'about:support' in address bar) to view the installed version number
    Affected if The version is below 128.7.0 or falls between 128.7.0 and 133.0 (excluding 133.0)
  2. Check Thunderbird version
    Navigate to Thunderbird menu > Help > About Thunderbird to view the installed version number
    Affected if The version is below 128.7.0, or is 129.0 or higher but below 133.0
  3. Determine if S/MIME encryption is in use
    In Thunderbird: go to Account Settings > End-to-End Encryption. In Firefox: check if the browser is used to view S/MIME encrypted webmail or documents
    Affected if S/MIME encryption is enabled and used, as the vulnerable code path is triggered when processing PKCS#7 encrypted content (S/MIME emails, encrypted attachments)
  4. Identify error conditions in PKCS#7 processing
    Monitor for crashes or memory errors when opening encrypted emails or attachments, or when certificates fail validation during decryption
    Affected if The double-free occurs during error path handling, so malformed encrypted content or certificate issues could trigger the vulnerability

You are affected if your Firefox version is below 133.0 (or below 128.7.0 for ESR-style releases) or your Thunderbird version is below 133.0, and you use S/MIME/encrypted email functionality that exercises the PKCS#7 decoder.

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 128.7.0 / 133.0 or later
Fixed in 128.7.0133.0
Interim mitigation

Upgrade to Firefox 133, Thunderbird 133, Firefox ESR 128.7, Thunderbird 128.7 or later versions to apply the security patch.

Recommended fix High confidence

Firefox 133.0 / Firefox ESR 128.7.0 / Thunderbird 133.0 / Thunderbird 128.7.0

  1. Upgrade Firefox to version 133.0 or later
  2. If using Firefox ESR, upgrade to version 128.7.0 or later
  3. Upgrade Thunderbird to version 133.0 or later
  4. If using an older Thunderbird ESR, upgrade to version 128.7.0 or later
  5. Restart the application after upgrading

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

Fix this in Firefox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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