CVE-2024-1552
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 · uneditedIncorrect code generation could have led to unexpected numeric conversions and potential undefined behavior.*Note:* This issue only affects 32-bit ARM devices. 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 · moderate confidenceThis is a JIT compiler code generation bug in Firefox, Firefox ESR, and Thunderbird affecting only 32-bit ARM devices. The incorrect code generation causes unexpected numeric conversions that can lead to undefined behavior, potentially allowing crashes or unexpected application state.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 your CPU architectureRun 'uname -m' on the command line. On 32-bit ARM systems, this will return 'armv7l' or similar 32-bit ARM identifiers. 64-bit ARM systems will return 'aarch64'.Affected if The output shows a 32-bit ARM architecture (armv7l, armhf, or similar) rather than 64-bit (aarch64). This CVE only affects 32-bit ARM devices.
-
Check Firefox versionRun 'firefox --version' or look in Firefox menu > Help > About Firefox. Note the full version number.Affected if The installed version is lower than 115.8.0 or between 115.8.0 and 123.0 (for example, 120.0, 122.0). Versions 123.0 and later, or 115.8.0 and later for ESR, are fixed.
-
Check Thunderbird version if applicableRun 'thunderbird --version' or look in Thunderbird menu > Help > About Thunderbird. Note the full version number.Affected if Thunderbird is installed and the version is lower than 115.8.0. Versions 115.8.0 and later are fixed.
-
Verify JavaScript JIT is enabledIn Firefox or Thunderbird, navigate to 'about:config' in the address bar, search for 'javascript.options.jit', and check if the value is set to 'true'.Affected if The preference 'javascript.options.jit' is set to true (this is the default). The vulnerability requires JIT to be enabled for the faulty code generation to occur.
You are affected if you are running an unpatched Firefox or Thunderbird version (below 115.8.0 or between 115.8.0 and 123.0) on a 32-bit ARM device with JavaScript/JIT enabled.
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 affected installations to Firefox 123+, Firefox ESR 115.8+, or Thunderbird 115.8+ on all 32-bit ARM devices. Alternatively, disable JavaScript or use alternative browsers on affected devices until upgrades are available.
Firefox 123.0 (or Firefox ESR 115.8.0); Thunderbird 115.8.0
- Check current Firefox version by navigating to about:Firefox or running 'firefox --version'
- Check current Thunderbird version by navigating to Help > About Thunderbird or running 'thunderbird --version'
- 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
- Verify the upgrade was successful by checking the version again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1552 — 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-1552 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