FirefoxWeb browser · Mozilla

CVE-2023-29536

HIGH · 8.8 CVSS v3.1 Published 2023-06-02
Fix available
A fix is available. Upgrade to 102.10 / 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
An attacker could cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, resulting in an assertion, memory corruption, or a potentially exploitable crash. This vulnerability affects Firefox < 112, Focus for Android < 112, Firefox ESR < 102.10, Firefox for Android < 112, and Thunderbird < 102.10.

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

A memory management flaw in Firefox and related products allows an attacker to cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, leading to assertion failures, memory corruption, or potentially exploitable crashes.

MitigationUpdate to Firefox 112, Firefox ESR 102.10, Firefox for Android 112, Focus for Android 112, Thunderbird 102.10, or later versions to patch this vulnerability.

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
Firefox EsrWeb browser
Affected:< 102.10
FocusApplication
Affected:< 112.0
ThunderbirdApplication
Affected:< 102.10

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 product
    Open the application and go to Help > About [Product Name], or check the installed version via command line: on Windows check Program Files, on macOS check /Applications, on Linux check your package manager
    Affected if The installed product is Firefox, Firefox ESR, Focus, or Thunderbird
  2. Determine Firefox version
    In Firefox, navigate to Help > About Firefox, or enter 'about:support' in the address bar
    Affected if Version is below 112.0 (for example, 111.x or earlier)
  3. Determine Firefox ESR version
    In Firefox ESR, navigate to Help > About Firefox, or enter 'about:support' in the address bar
    Affected if Version is below 102.10 (for example, 102.9.x or earlier)
  4. Determine Thunderbird version
    In Thunderbird, navigate to Help > About Thunderbird, or enter 'about:support' in the address bar
    Affected if Version is below 102.10 (for example, 102.9.x or earlier)
  5. Determine Focus for Android version
    Open the Google Play Store app, go to My apps & games, find Focus, and check the version number listed
    Affected if Version is below 112.0 (for example, 111.x or earlier)

Your environment is affected if any installed Mozilla product (Firefox, Firefox ESR, Focus, or Thunderbird) has a version number lower than 112.0 or 102.10 respectively.

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

Update to Firefox 112, Firefox ESR 102.10, Firefox for Android 112, Focus for Android 112, Thunderbird 102.10, or later versions to patch this vulnerability.

Recommended fix High confidence

Firefox 112.0, Firefox ESR 102.10, Focus 112.0, Thunderbird 102.10

  1. Upgrade Firefox to version 112.0 or later
  2. Upgrade Firefox ESR to version 102.10 or later
  3. Upgrade Focus for Android to version 112.0 or later
  4. Upgrade Thunderbird to version 102.10 or later
  5. For Firefox for Android, upgrade to version 112.0 or later

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29536 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