FirefoxWeb browser · Mozilla
CVE-2023-29544
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 · uneditedIf multiple instances of resource exhaustion occurred at the incorrect time, the garbage collector could have caused memory corruption and a potentially exploitable crash. This vulnerability affects Firefox for Android < 112, Firefox < 112, and Focus for Android < 112.
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 confidenceA garbage collector timing vulnerability in Firefox allows memory corruption when multiple resource exhaustion instances occur simultaneously at a specific moment, potentially leading to exploitable crashes. The issue stems from incorrect garbage collector behavior under specific memory pressure conditions.
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
< 112.0< 112.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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 desktop versionOpen Firefox and navigate to Help > About Firefox, or type about:support in the address bar. The version number appears at the top of the page.Affected if Version shown is less than 112.0 (for example, 111.0, 110.x, or earlier)
-
Check Mozilla Focus versionOpen Focus for Android, tap the three-dot menu, select Settings, then tap About Firefox Focus. The version is displayed on that screen.Affected if Version shown is less than 112.0 (for example, 111.0, 110.x, or earlier)
-
Verify garbage collector is activeThe JavaScript garbage collector runs by default in all Firefox installations. This is not a module that can be manually disabled through standard user settings.Affected if The affected version is running, meaning the vulnerable garbage collector timing behavior is present regardless of configuration
You are affected if Mozilla Firefox or Mozilla Focus is installed at any version below 112.0, since the vulnerable garbage collector timing behavior exists in those versions.
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 · scoped112.0
Update Firefox, Firefox for Android, and Focus for Android to version 112 or later to receive the garbage collector fix.
Firefox 112.0 and Focus for Android 112.0
- Check current Firefox or Focus version via Menu > Help > About Firefox/Focus
- If version is below 112.0, apply the update: Menu > Help > About Firefox/Focus will trigger an automatic check and download of the latest version
- If automatic updates are disabled, download Firefox 112.0 or Focus 112.0 from the official Mozilla download page (www.mozilla.org)
- Install the update and restart the application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29544 — 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-2023-29544 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