CVE-2024-11700
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 · uneditedMalicious websites may have been able to perform user intent confirmation through tapjacking. This could have led to users unknowingly approving the launch of external applications, potentially exposing them to underlying vulnerabilities. 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 confidenceThis is a tapjacking vulnerability in Firefox and Thunderbird where malicious websites could overlay their content on top of external application launch confirmation dialogs, tricking users into unknowingly approving the launch of potentially malicious external applications. The attack bypasses user intent confirmation by obscuring the actual confirmation dialog with deceptive content.
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< 133.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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Check installed Firefox versionOpen Firefox and navigate to Menu > Help > About Firefox, or enter 'about:support' in the address bar, or run 'firefox --version' from command lineAffected if The version displayed is below 133.0 (for example, 132.x or earlier)
-
Check installed Thunderbird versionOpen Thunderbird and navigate to Menu > Help > About Thunderbird, or run 'thunderbird --version' from command lineAffected if The version displayed is below 133.0 (for example, 132.x or earlier)
-
Verify external application launch is configured in FirefoxGo to Firefox Settings > General > Applications section. Look for 'External Protocol Links' entries such as 'mailto', 'ssh', or other protocol handlersAffected if Any external application handler is configured to 'Use' an external application (rather than set to 'Always ask' or 'Block'), and the Firefox version is below 133.0
-
Verify external application launch is configured in ThunderbirdGo to Thunderbird Settings > General > Attachments panel. Check both 'Incoming' and 'Outgoing' tabs for external application handlersAffected if Any external application handler is configured to open automatically (not set to 'Save' or 'Ask me'), and the Thunderbird version is below 133.0
You are affected if you run Firefox or Thunderbird version below 133.0 AND have configured external application handlers that can launch without user confirmation.
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 · scoped133.0
Upgrade to Firefox 133 or Thunderbird 133 or later to receive the security patch that addresses this tapjacking vulnerability in external application launch confirmations.
Firefox 133.0, Thunderbird 133.0
- Open Firefox and navigate to Menu > Help > About Firefox to trigger automatic update check
- After update completes, verify the version shows 133.0 or later in the About dialog
- For Thunderbird, open Menu > Help > About Thunderbird and verify version 133.0 or later
- If automatic updates are unavailable, download Firefox 133.0 from www.mozilla.org and Thunderbird 133.0 from www.thunderbird.net
- Restart the applications after installation to ensure the update is fully applied
- Verify the installed version is 133.0 or later in the About dialog for each application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11700 — 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-11700 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