CVE-2024-10460
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 · uneditedThe origin of an external protocol handler prompt could have been obscured using a data: URL within an `iframe`. This vulnerability affects Firefox < 132, Firefox ESR < 128.4, Thunderbird < 128.4, and Thunderbird < 132.
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 confidenceThe browser's external protocol handler prompt (e.g., for launching external applications like mailto: or tel: handlers) could have its origin information obscured by embedding a data: URL within an iframe, potentially tricking users into trusting a malicious external application launch request.
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< 128.4.0< 132.0< 128.4>= 129, < 132CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox versionNavigate to Firefox, click the menu button, select Help, then About Firefox. The version number is displayed on this page.Affected if The installed version is below 128.4.0 or below 132.0 (for example, 128.3.x, 131.x, or any 128.x version below 128.4.0)
-
Check Thunderbird versionNavigate to Thunderbird, click the menu button, select Help, then About Thunderbird. The version number is displayed on this page.Affected if The installed version is below 128.4, or is 129.x or any version from 130.0 through 131.x (but not 132.0 or higher)
-
Confirm product typeIdentify whether the detected application is Firefox (web browser) or Thunderbird (email client). This matters because they have different version numbering for the fix.Affected if Either product is found and its version falls into the vulnerable ranges listed above
A user is affected if they run Mozilla Firefox below 128.4.0 or below 132.0, or Mozilla Thunderbird below 128.4 or between 129.0 and 131.x, as these versions contain the UI spoofing flaw in the external protocol handler prompt.
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 · scoped128.4128.4.0132
Upgrade to Firefox 132, Firefox ESR 128.4, Thunderbird 128.4, or Thunderbird 132 to resolve this UI spoofing vulnerability.
Firefox 132.0 (or Firefox ESR 128.4.0); Thunderbird 132 (or 128.4)
- Upgrade Firefox to version 132.0 or later if currently on 129.x-131.x
- Upgrade Firefox to version 128.4.0 or later if currently on 128.x or earlier (ESR or release)
- Upgrade Thunderbird to version 132 or later if currently on 129.x-131.x
- Upgrade Thunderbird to version 128.4 or later if currently on 128.x or earlier
- After upgrading, verify the version in Help > About Firefox/Thunderbird
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10460 — 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-10460 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