FirefoxWeb browser · Mozilla
CVE-2024-5696
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 · uneditedBy manipulating the text in an `<input>` tag, an attacker could have caused corrupt memory leading to a potentially exploitable crash. This vulnerability affects Firefox < 127, Firefox ESR < 115.12, and Thunderbird < 115.12.
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 memory corruption vulnerability exists in Firefox and Thunderbird where manipulating text within an HTML input tag can cause corrupt memory, leading to a potentially exploitable crash. The vulnerability stems from improper handling of input tag text rendering.
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
< 115.12< 127.0
Debian LinuxOperating system
= 10.0< 115.12CVSS 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
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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, go to Help > About Firefox, or run 'firefox --version' in terminalAffected if Version is below 115.12 or between 115.12 and 127.0 (exclusive)
-
Check Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird, or run 'thunderbird --version' in terminalAffected if Version is below 115.12
-
Check Debian system versionRun 'cat /etc/debian_version' in terminalAffected if Version is 10.0 and affected Mozilla products are installed
-
Verify HTML input field usageThis vulnerability triggers when manipulating text in HTML input tags - a common web form interaction; any user browsing web forms with input fields in affected versions is potentially affectedAffected if Using affected Firefox or Thunderbird version while interacting with HTML input fields
User is affected if Firefox version is < 115.12 or >= 115.12 but < 127.0, or Thunderbird version is < 115.12, and they interact with text in HTML input fields.
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.12127.0
Update affected installations to Firefox 127 or later, Firefox ESR 115.12 or later, or Thunderbird 115.12 or later to remediate this vulnerability.
Firefox 127 / Firefox ESR 115.12 / Thunderbird 115.12
- Upgrade Firefox to version 127 or later (or Firefox ESR 115.12 or later if using the ESR release)
- Upgrade Thunderbird to version 115.12 or later
- After upgrading, verify the browser version by navigating to about:support (Firefox) or Help > About Thunderbird (Thunderbird)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5696 — 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-5696 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