dbcve.org
FirefoxWeb browser · Mozilla

CVE-2023-29551

HIGH · 8.8 CVSS v3.1 Published 2023-06-02
Fix available
A fix is available. Upgrade to 112.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Memory safety bugs present in Firefox 111. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. 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 · high confidence

Memory safety bugs in Firefox 111 allow memory corruption that could potentially be exploited for arbitrary code execution. The vulnerability affects multiple Firefox products for Android and desktop platforms.

MitigationUpgrade to Firefox 112 or later, or Firefox for Android 112 or later, or Focus for Android 112 or later to address the memory corruption vulnerabilities.

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:< 112.0
FocusApplication
Affected:< 112.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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Identify installed Mozilla products
    Check for installed Firefox or Focus browsers on the system. On desktop: look for Firefox in Program Files (Windows) or /Applications (macOS) or /usr/lib/firefox (Linux). On Android: check installed apps for Firefox or Focus.
    Affected if Either Firefox or Focus is installed on the system or device.
  2. Determine Firefox version
    In Firefox: navigate to menu > Help > About Firefox. On Linux terminal: 'firefox --version' or check /usr/lib/firefox/browser/chrome/browser/content/browser/aboutDialog.xhtml for version. On Windows: check registry key HKLM\SOFTWARE\Mozilla\Mozilla Firefox\CurrentVersion or the file properties of firefox.exe.
    Affected if The displayed version number is less than 112.0 (e.g., 111.0, 110.0, etc.).
  3. Determine Mozilla Focus version
    On Android: go to Settings > Apps > Mozilla Focus > App info to view version. On iOS: check App Store listing or the app version in Settings.
    Affected if The displayed version number is less than 112.0.
  4. Confirm vulnerability applicability
    This vulnerability is a memory safety issue in the browser engine itself. It does not depend on specific configurations, extensions, or user settings. Any Firefox or Focus version below 112.0 running as a browser is potentially vulnerable.
    Affected if The installed Firefox or Focus version is below 112.0 and the browser is actively used or running.

If either Mozilla Firefox or Mozilla Focus is installed and its version is below 112.0, the environment is affected by this CVE.

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 112.0 or later
Fixed in 112.0
Interim mitigation

Upgrade to Firefox 112 or later, or Firefox for Android 112 or later, or Focus for Android 112 or later to address the memory corruption vulnerabilities.

Recommended fix High confidence

Firefox 112.0, Focus for Android 112.0

  1. Check current Firefox or Focus version (Firefox: Help > About Firefox; Focus: Settings > About)
  2. Download Firefox 112.0 or later from mozilla.org
  3. Install the updated Firefox version
  4. For Android devices, update Focus via Google Play Store or install Focus 112.0 or later
  5. Restart the browser after update

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
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29551 — 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-2023-29551 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