dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-1551

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-20
Fix available
A fix is available. Upgrade to 115.8.0 / 123.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Public exploit 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
Set-Cookie response headers were being incorrectly honored in multipart HTTP responses. If an attacker could control the Content-Type response header, as well as control part of the response body, they could inject Set-Cookie response headers that would have been honored by the browser. 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

A detailed technical summary for this CVE is being prepared.

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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
Recommended fix High confidence

Firefox 123.0 (or ESR 115.8.0); Thunderbird 115.8.0

  1. Check current Firefox or Thunderbird version by navigating to Help > About (or using about:support in Firefox, about:thunderbird in Thunderbird)
  2. For Firefox: Navigate to https://www.mozilla.org/firefox/all/ and download version 123.0 or later for release, or 115.8.0 or later for ESR
  3. For Thunderbird: Navigate to https://www.thunderbird.net/en-US/ and download version 115.8.0 or later
  4. Close all instances of Firefox/Thunderbird before installing
  5. Run the installer and follow prompts to complete the upgrade
  6. Restart the browser/mail client after installation completes
  7. Verify the installed version matches the fixed release (Firefox 123.0+, Firefox ESR 115.8.0+, or Thunderbird 115.8.0+)
Caveat No major breaking changes expected for standard users; extensions may need verification for compatibility with new major versions

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1551 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-1551 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