FirefoxWeb browser · Mozilla

CVE-2023-5724

HIGH · 7.5 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to 115.4 / 115.4.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Drivers are not always robust to extremely large draw calls and in some cases this scenario could have led to a crash. This vulnerability affects Firefox < 119, Firefox ESR < 115.4, and Thunderbird < 115.4.1.

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

This is a denial-of-service vulnerability in the graphics rendering subsystem of Firefox, Firefox ESR, and Thunderbird. The browsers fail to properly handle extremely large draw calls, causing a crash due to insufficient robustness in the graphics driver handling.

MitigationUpdate Firefox to version 119 or later, Firefox ESR to 115.4 or later, and Thunderbird to 115.4.1 or later to remediate 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:< 119.0
Firefox EsrWeb browser
Affected:< 115.4
Debian LinuxOperating system
Affected:= 10.0= 11.0
ThunderbirdApplication
Affected:< 115.4.1

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Mozilla product and version
    For Firefox: Type 'about:support' in the address bar and note the Version listed under Application Basics. For Thunderbird: Go to Help > About and note the version number. On Linux, you can also run 'firefox --version' or 'thunderbird --version' in terminal.
    Affected if The product is Firefox, Firefox ESR, or Thunderbird and the version is below the fixed releases (119.0 for Firefox, 115.4 for ESR, 115.4.1 for Thunderbird)
  2. Confirm graphics rendering is enabled
    In Firefox, go to about:preferences and scroll to Performance, or type 'about:support' and check the Graphics section. Verify that 'Hardware Acceleration' is enabled. For Thunderbird, graphics rendering is used when viewing HTML messages or using compose features.
    Affected if Hardware acceleration or WebGL is enabled (this is the default state in affected versions)

You are affected if you are running Firefox < 119.0, Firefox ESR < 115.4, or Thunderbird < 115.4.1 with graphics rendering enabled (the default configuration).

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 115.4 / 115.4.1 / 119.0 or later
Fixed in 115.4115.4.1119.0
Interim mitigation

Update Firefox to version 119 or later, Firefox ESR to 115.4 or later, and Thunderbird to 115.4.1 or later to remediate this vulnerability.

Recommended fix High confidence

Firefox 119.0, Firefox ESR 115.4, or Thunderbird 115.4.1

  1. Check current version of Firefox, Firefox ESR, or Thunderbird by navigating to Help > About (or using 'firefox --version' / 'thunderbird --version' in terminal)
  2. Download Firefox 119.0 (or later) from the official Mozilla website or your system's package manager
  3. For Firefox ESR users, upgrade to version 115.4 or later
  4. For Thunderbird users, upgrade to version 115.4.1 or later
  5. Restart the application after upgrading to ensure the new version is active
  6. Verify the fix by checking the About section shows the updated version number
Caveat Standard Mozilla release upgrades typically have minimal breaking changes; however, some extensions or settings may not be compatible with the new major version

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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