FirefoxWeb browser · Mozilla
CVE-2024-11694
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 · uneditedEnhanced Tracking Protection's Strict mode may have inadvertently allowed a CSP `frame-src` bypass and DOM-based XSS through the Google SafeFrame shim in the Web Compatibility extension. This issue could have exposed users to malicious frames masquerading as legitimate content. This vulnerability affects Firefox < 133, Firefox ESR < 128.5, Firefox ESR < 115.18, Thunderbird < 133, Thunderbird < 128.5, and Thunderbird < 115.18.
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 confidenceEnhanced Tracking Protection's Strict mode in Firefox and Thunderbird contained a flaw in the Web Compatibility extension's Google SafeFrame shim that allowed CSP frame-src directives to be bypassed, enabling DOM-based XSS. This could permit malicious iframes to execute content as if from legitimate sources.
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
< 115.8.0< 133.0>= 116.0, < 128.5.0< 115.18.0>= 116.0, < 128.5.0>= 129.0, < 133.0CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed application and versionOpen Firefox or Thunderbird, go to Help > About (or use menu: Help > About Thunderbird). Note the exact version number displayed.Affected if The version falls outside the safe versions: Firefox 133.0+, 128.5.0+, or 115.8.0+; Thunderbird 133.0+, 128.5.0+, or 115.18.0+.
-
Confirm Enhanced Tracking Protection Strict mode is enabledIn Firefox: Go to Settings > Privacy & Security > Enhanced Tracking Protection and verify Strict is selected. In Thunderbird: Go to Settings > Privacy & Security > Tracking Protection and verify Strict is selected.Affected if Enhanced Tracking Protection is set to Strict mode, as this is required for the vulnerable Google SafeFrame shim to be active.
-
Verify Web Compatibility module is activeThe Web Compatibility module is bundled with Enhanced Tracking Protection. In Strict mode, it automatically includes the Google SafeFrame shim. No separate config check needed if Strict mode is confirmed in step 2.Affected if Enhanced Tracking Protection Strict mode is enabled, which loads the Web Compatibility extension containing the vulnerable shim.
You are affected if your Firefox or Thunderbird version is below the safe thresholds AND Enhanced Tracking Protection is set to Strict mode, enabling the vulnerable Google SafeFrame shim that can bypass CSP frame-src directives.
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 · scoped115.8.0115.18.0128.5.0
Update affected installations to Firefox 133+, Firefox ESR 128.5+/115.18+, or Thunderbird 133+/128.5+/115.18+ to receive the patch.
Firefox 133.0+ / Firefox ESR 128.5.0+ / Firefox ESR 115.18.0+ / Thunderbird 133.0+ / Thunderbird 128.5.0+ / Thunderbird 115.18.0+
- 1. Check current Firefox or Thunderbird version by clicking Help > About Firefox or Help > About Thunderbird
- 2. If the version is affected (Firefox < 133.0 or Firefox ESR < 128.5.0 or < 115.18.0; Thunderbird < 133.0 or < 128.5.0 or < 115.18.0), download the fixed version from https://www.mozilla.org/
- 3. Install the update by running the downloaded installer
- 4. Restart the application to complete the update
- 5. Verify the version has been updated to a fixed release (Firefox 133.0+, Firefox ESR 128.5.0+, Firefox ESR 115.18.0+, Thunderbird 133.0+, Thunderbird 128.5.0+, or Thunderbird 115.18.0+)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11694 — 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-11694 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