CVE-2023-4582
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 · uneditedDue to large allocation checks in Angle for glsl shaders being too lenient a buffer overflow could have occurred when allocating too much private shader memory on mac OS. *This bug only affects Firefox on macOS. Other operating systems are unaffected.* This vulnerability affects Firefox < 117, Firefox ESR < 115.2, and Thunderbird < 115.2.
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 confidenceA buffer overflow vulnerability exists in the Angle graphics translation layer used by Firefox on macOS. The allocation checks for private shader memory in GLSL shaders are too lenient, allowing excessive memory allocation that triggers a buffer overflow when processing specially crafted shader code.
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< 117.0< 115.2< 115.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the operating systemRun 'sw_vers' or check System Settings to confirm the OS is macOS. This vulnerability only affects macOS; other operating systems are not impacted.Affected if The OS is anything other than macOS (users on Windows, Linux, etc. are not affected by this specific CVE).
-
Confirm installed product and version - FirefoxOpen Firefox, go to Firefox > About Firefox to view the version number. Alternatively, run '/Applications/Firefox.app/Contents/MacOS/firefox --version' in Terminal.Affected if The displayed version is lower than 117.0 (for example, 116.x, 115.x, or earlier).
-
Confirm installed product and version - Firefox ESROpen Firefox ESR, go to Firefox > About Firefox ESR to view the version number. Alternatively, run '/Applications/Firefox ESR.app/Contents/MacOS/firefox --version' in Terminal.Affected if The displayed version is lower than 115.2 (for example, 115.1, 115.0, or earlier).
-
Confirm installed product and version - ThunderbirdOpen Thunderbird, go to Thunderbird > About Thunderbird to view the version number. Alternatively, run '/Applications/Thunderbird.app/Contents/MacOS/thunderbird --version' in Terminal.Affected if The displayed version is lower than 115.2 (for example, 115.1, 115.0, or earlier).
You are affected if you are running Firefox below 117.0, Firefox ESR below 115.2, or Thunderbird below 115.2 on macOS, and you process specially crafted GLSL shader code through the Angle graphics layer.
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 · scoped115.2117.0
Update Firefox to version 117 or later, Firefox ESR to 115.2 or later, or Thunderbird to 115.2 or later. This vulnerability only affects macOS; other operating systems are not impacted.
Firefox 117.0, Firefox ESR 115.2, Thunderbird 115.2
- 1. Identify the installed product (Firefox or Firefox ESR or Thunderbird) and current version via Help > About (or Thunderbird > About Thunderbird on macOS)
- 2. Navigate to https://www.mozilla.org/ for Firefox, or https://www.thunderbird.net/ for Thunderbird
- 3. Download the appropriate fixed version: Firefox 117.0 or later, Firefox ESR 115.2 or later, or Thunderbird 115.2 or later
- 4. Close all instances of the application
- 5. Run the installer and follow prompts to complete the upgrade
- 6. Restart the browser/mail client
- 7. Verify the version by checking Help > About to confirm the installed version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4582 — 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-4582 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