CVE-2024-9680
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 was able to achieve code execution in the content process by exploiting a use-after-free in Animation timelines. We have had reports of this vulnerability being exploited in the wild. This vulnerability affects Firefox < 131.0.2, Firefox ESR < 128.3.1, Firefox ESR < 115.16.1, Thunderbird < 131.0.1, Thunderbird < 128.3.1, and Thunderbird < 115.16.0.
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 the Animation timelines component allows attackers to achieve arbitrary code execution in the Firefox/Thunderbird content process. This memory corruption flaw has been observed being actively exploited in the wild.
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.16.1< 131.0.2>= 128.1.0, < 128.3.1= 11.0< 115.16.0>= 128.0.1, < 128.3.1= 131.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox browser versionRun 'firefox --version' from command line, or on Windows check Help > About Firefox, or on macOS from Firefox menu > About FirefoxAffected if version is below 115.16.1, or below 131.0.2, or between 128.1.0 and 128.3.0 inclusive
-
Check Thunderbird email client versionRun 'thunderbird --version' from command line, or check Help > About ThunderbirdAffected if version is below 115.16.0, or between 128.0.1 and 128.3.0 inclusive, or exactly 131.0
-
Check installed package version on Debian LinuxRun 'dpkg -l | grep -i firefox' or 'apt-cache policy firefox' to see the installed package versionAffected if firefox package version indicates an affected release (versions below 115.16.1, 128.x before 128.3.1, or 131.x before 131.0.2)
You are affected if any installed Firefox or Thunderbird version falls within the vulnerable ranges: Firefox < 115.16.1, < 131.0.2, or 128.1.0-128.3.0; Thunderbird < 115.16.0, 128.0.1-128.3.0, or exactly 131.0
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.16.0115.16.1128.3.1
Immediately update affected installations to Firefox 131.0.2, Firefox ESR 128.3.1/115.16.1, or Thunderbird 131.0.1/128.3.1/115.16.0 or later to remediate this critical vulnerability.
Firefox 131.0.2+, Firefox ESR 128.3.1+, Firefox ESR 115.16.1+, Thunderbird 128.3.1+, Thunderbird 115.16.0+, Thunderbird 131.0.2+
- Check current Firefox version: Navigate to Menu > Help > About Firefox (or enter 'about:firefox' in address bar)
- Check current Thunderbird version: Navigate to Menu > Help > About Thunderbird
- For Firefox: Upgrade to version 131.0.2 or later for mainstream, 128.3.1 or later for ESR 128.x, or 115.16.1 or later for ESR 115.x
- For Thunderbird: Upgrade to version 128.3.1 or later for ESR 128.x, or 115.16.0 or later for ESR 115.x, or 131.0.2 for mainstream
- On Linux: Run 'sudo apt-get update && sudo apt-get upgrade' for Debian-based distributions, or use your system's package manager
- On Windows/macOS: Use automatic updates or download from https://www.mozilla.org/
- Verify the update was successful by checking the About page again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9680 — 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-9680 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