FirefoxWeb browser · Mozilla

CVE-2024-1546

HIGH · 7.5 CVSS v3.1 Published 2024-02-20
Fix available
A fix is available. Upgrade to 115.8.0 / 123.0 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
When 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 confidence

Buffer 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.

MitigationUpgrade to Firefox 123, Firefox ESR 115.8, Thunderbird 115.8 or later to remediate this out-of-bounds read vulnerability.

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
FirefoxWeb browser
Affected:< 115.8.0< 123.0
Debian LinuxOperating system
Affected:= 10.0
ThunderbirdApplication
Affected:< 115.8.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Firefox version
    Open Firefox and navigate to Help > About Firefox, or run 'firefox --version' from command line
    Affected if Version is less than 115.8.0 or between 116.0 and 122.x (i.e., less than 123.0)
  2. Check Thunderbird version
    Open Thunderbird and navigate to Help > About Thunderbird, or run 'thunderbird --version' from command line
    Affected if Version is less than 115.8.0
  3. Verify Debian 10 Mozilla package
    On Debian 10.0 systems, run 'dpkg -l | grep -i mozilla' or check installed packages via package manager
    Affected if Mozilla Firefox or Thunderbird packages from Debian 10.0 repositories are installed (these ship older vulnerable versions)
  4. Confirm networking feature usage
    The vulnerability exists in the networking channel - any network activity (HTTP/HTTPS requests, WebSocket, fetch API) uses this component
    Affected 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.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 115.8.0 / 123.0 or later
Fixed in 115.8.0123.0
Interim mitigation

Upgrade to Firefox 123, Firefox ESR 115.8, Thunderbird 115.8 or later to remediate this out-of-bounds read vulnerability.

Recommended fix High confidence

Firefox 123.0 (or Firefox ESR 115.8.0); Thunderbird 115.8.0

  1. For Firefox: Upgrade to version 123.0 or later (or Firefox ESR 115.8.0 or later)
  2. For Thunderbird: Upgrade to version 115.8.0 or later
  3. 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.
Caveat Users on Debian 10 will need to upgrade to Debian 11/12 as Debian 10 is end-of-life and receives no further security updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

Check 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1546 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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