dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-6600

MEDIUM · 6.3 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 115.13 / 128.0 or later.
See remediation →
70/100
Remediation priority · Elevated
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
Due to large allocation checks in Angle for GLSL shaders being too lenient an out-of-bounds access could occur when allocating more than 8192 ints in private shader memory on macOS. This vulnerability affects Firefox < 128, Firefox ESR < 115.13, Thunderbird < 115.13, and Thunderbird < 128.

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 bounds checking vulnerability in the Angle graphics layer allows out-of-bounds memory access on macOS when GLSL shaders allocate more than 8192 integers in private shader memory. The allocation validation is too lenient, permitting allocations that exceed safe buffer boundaries.

MitigationUpdate affected Mozilla products (Firefox, Firefox ESR, Thunderbird) to version 128 or higher (or 115.13+ for ESR/Thunderbird legacy branches) to receive the patched allocation bounds checking in the Angle component.

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:< 115.13< 128.0
ThunderbirdApplication
Affected:< 115.13>= 116.0, < 128.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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

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
    Check if Firefox or Thunderbird is installed by looking for the application in /Applications or checking via system_profiler SPApplicationsDataType
    Affected if The product is Firefox or Thunderbird on macOS
  2. Determine the installed product version
    For Firefox: open the application and go to Firefox > About Firefox, or check the Info.plist file at /Applications/Firefox.app/Contents/Info.plist for CFBundleShortVersionString. For Thunderbird: go to Thunderbird > About Thunderbird or check /Applications/Thunderbird.app/Contents/Info.plist
    Affected if Version is earlier than 115.13, or between 116.0 and 127.x (below 128.0)
  3. Confirm the operating system is macOS
    Run 'uname -a' or check system_profiler SPSoftwareDataType to verify the OS is macOS
    Affected if Running on macOS (this vulnerability only affects macOS)
  4. Verify the Angle graphics layer is in use
    In Firefox/Thunderbird, navigate to about:support and look for 'GPU #1' under Graphics. The 'Compositing' field will show 'Basic' or 'WebGL' using Angle if the feature is active. This is enabled by default on macOS.
    Affected if Angle is being used for WebGL or graphics rendering (enabled by default on macOS)

The environment is affected if running Firefox or Thunderbird on macOS with a version earlier than 115.13 or between 116.0 and 127.x, where the Angle graphics layer handles shader allocations.

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.13 / 128.0 or later
Fixed in 115.13128.0
Interim mitigation

Update affected Mozilla products (Firefox, Firefox ESR, Thunderbird) to version 128 or higher (or 115.13+ for ESR/Thunderbird legacy branches) to receive the patched allocation bounds checking in the Angle component.

Recommended fix High confidence

Firefox 128.0 (stable), Firefox ESR 115.13 (ESR), Thunderbird 115.13 or 128.0 (depending on current branch)

  1. Check current Firefox or Thunderbird version via Help > About (or running 'firefox --version' / 'thunderbird --version' in terminal)
  2. For Firefox stable: upgrade to version 128.0 or later
  3. For Firefox ESR: upgrade to version 115.13 or later
  4. For Thunderbird: if version < 115.13, upgrade to 115.13; if version >= 116.0 and < 128.0, upgrade to 128.0
  5. Download from official Mozilla site (www.mozilla.org) or use built-in update mechanism via Help > Check for Updates
  6. Restart the application after updating
Caveat Minor release upgrades typically have no breaking changes; some older extensions/add-ons may be incompatible

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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