CVE-2024-10459
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 · uneditedAn attacker could have caused a use-after-free when accessibility was enabled, leading to a potentially exploitable crash. This vulnerability affects Firefox < 132, Firefox ESR < 128.4, Firefox ESR < 115.17, 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 confidenceA use-after-free vulnerability in Mozilla Firefox and Thunderbird that triggers when accessibility features are enabled, allowing a remote attacker to potentially exploit memory corruption and cause a crash.
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< 115.17< 132.0>= 116.0, < 128.4.0< 128.4.0>= 129.0, < 132.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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Mozilla productDetermine if Firefox or Thunderbird is installed. On Linux, check for /usr/bin/firefox or /usr/bin/thunderbird. On Windows, check Program Files for Mozilla Firefox or Mozilla Thunderbird folders.Affected if The product is Mozilla Firefox or Thunderbird
-
Check the installed Firefox versionRun 'firefox --version' or open Firefox and navigate to about:support to view the version number.Affected if Firefox version is before 115.17, before 132.0, or between 116.0 and 128.4.0 (excluding 128.4.0)
-
Check the installed Thunderbird versionRun 'thunderbird --version' or open Thunderbird and navigate to Help > About Thunderbird to view the version number.Affected if Thunderbird version is before 128.4.0 or between 129.0 and 132.0 (excluding 132.0)
-
Verify if accessibility features are enabledIn Firefox: Go to Settings > Accessibility and check if 'Always use accessibility features' is enabled. In Thunderbird: Go to Settings > Advanced > General and check 'Always enable accessibility features'. Alternatively, check for the accessibility.service.enabled preference in about:config set to true.Affected if Accessibility features are turned on or enabled in the application settings
A user is affected if they have Firefox or Thunderbird installed with a version matching the affected ranges AND have accessibility features enabled, since the vulnerability only triggers under that specific configuration.
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.17128.4.0132.0
Update affected Firefox and Thunderbird installations to version 132 or later (Firefox ESR to 128.4/115.17 or later) to apply the vendor patch.
Firefox 132.0 (or Firefox ESR 128.4.0 / Firefox ESR 115.17); Thunderbird 132.0 (or Thunderbird 128.4.0)
- Check current Firefox or Thunderbird version via Help > About (or running: firefox --version or thunderbird --version)
- For Firefox users on version < 115.17: Upgrade to Firefox 115.17 or later
- For Firefox users on versions 116.0 to <128.4.0: Upgrade to Firefox 128.4.0 or later
- For Firefox users on versions >=128.4.0 but <132.0: Upgrade to Firefox 132.0 or later
- For Thunderbird users on version <128.4.0: Upgrade to Thunderbird 128.4.0 or later
- For Thunderbird users on versions 129.0 to <132.0: Upgrade to Thunderbird 132.0 or later
- Restart the application after upgrade
- Verify the new version is installed by checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- 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-10459 — 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-10459 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