CVE-2024-10467
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 · uneditedMemory safety bugs present in Firefox 131, Firefox ESR 128.3, and Thunderbird 128.3. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. 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 confidenceMultiple memory safety bugs in Firefox 131, Firefox ESR 128.3, and Thunderbird 128.3 allowed memory corruption that could potentially be exploited for arbitrary code execution. These are classic memory corruption vulnerabilities (likely use-after-free, buffer overflows, or similar) in the browser's memory management.
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.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify the installed Mozilla productCheck what Mozilla application is installed: look for 'Firefox' or 'Thunderbird' in installed programs, or run 'firefox --version' or 'thunderbird --version' in terminalAffected if The product is Firefox or Thunderbird
-
Get the Firefox version numberFor Firefox: go to Menu > Help > About Firefox, or run 'firefox --version' in command lineAffected if Version is less than 128.4.0 or between 128.4.0 and 132.0 (exclusive)
-
Get the Thunderbird version numberFor Thunderbird: go to Menu > Help > About Thunderbird, or run 'thunderbird --version' in command lineAffected if Version is less than 128.4.0 or between 129.0 and 132.0 (exclusive)
You are affected if Firefox is any version below 128.4.0 or below 132.0, or if Thunderbird is any version below 128.4.0 or between 129.0 and 132.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 · scoped128.4.0132.0
Upgrade to Firefox 132+, Firefox ESR 128.4+, Thunderbird 128.4+, or Thunderbird 132+ to obtain the memory safety fixes.
Firefox 132.0, Firefox ESR 128.4.0, Thunderbird 128.4.0, or Thunderbird 132.0 (depending on product and track)
- Identify the currently installed Firefox or Thunderbird version by navigating to Help > About (or using the application menu)
- Determine which track the installation follows: Firefox Stable, Firefox ESR, or Thunderbird
- For Firefox Stable < 132: Upgrade to Firefox 132.0 or later
- For Firefox ESR < 128.4: Upgrade to Firefox ESR 128.4.0 or later
- For Thunderbird < 128.4: Upgrade to Thunderbird 128.4.0 or later
- For Thunderbird >= 129.0 and < 132: Upgrade to Thunderbird 132.0 or later
- After upgrading, restart the application to apply the fix
- Verify the installed version matches or exceeds the fixed release
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-10467 — 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-10467 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