CVE-2024-1546
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 · uneditedWhen storing and re-accessing data on a networking channel, the length of buffers may have been confused, resulting in an out-of-bounds memory read. This vulnerability affects Firefox < 123, Firefox ESR < 115.8, and Thunderbird < 115.8.
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 confidenceBuffer length confusion in the networking channel of Firefox and Thunderbird allows out-of-bounds memory reads when storing and re-accessing data, potentially exposing sensitive memory contents to remote attackers.
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.8.0< 123.0= 10.0< 115.8.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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Check Firefox versionOpen Firefox and navigate to Help > About Firefox, or run 'firefox --version' from command lineAffected if Version is less than 115.8.0 or between 116.0 and 122.x (i.e., less than 123.0)
-
Check Thunderbird versionOpen Thunderbird and navigate to Help > About Thunderbird, or run 'thunderbird --version' from command lineAffected if Version is less than 115.8.0
-
Verify Debian 10 Mozilla packageOn Debian 10.0 systems, run 'dpkg -l | grep -i mozilla' or check installed packages via package managerAffected if Mozilla Firefox or Thunderbird packages from Debian 10.0 repositories are installed (these ship older vulnerable versions)
-
Confirm networking feature usageThe vulnerability exists in the networking channel - any network activity (HTTP/HTTPS requests, WebSocket, fetch API) uses this componentAffected if The browser or mail client is used for any network communications, which is the default and always-on state
You are affected if you run Firefox versions below 115.8.0 or between 116.0-122.x, or Thunderbird below 115.8.0, particularly on Debian 10.0 systems with bundled Mozilla products.
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.8.0123.0
Upgrade to Firefox 123, Firefox ESR 115.8, Thunderbird 115.8 or later to remediate this out-of-bounds read vulnerability.
Firefox 123.0 (or Firefox ESR 115.8.0); Thunderbird 115.8.0
- For Firefox: Upgrade to version 123.0 or later (or Firefox ESR 115.8.0 or later)
- For Thunderbird: Upgrade to version 115.8.0 or later
- For Debian 10 (Buster): This release reached end-of-life in June 2022 and no longer receives security updates. Upgrade to Debian 11 (Bullseye) or Debian 12 (Bookworm) to obtain the fixed Firefox/Thunderbird packages.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1546 — 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-1546 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