ChromeWeb browser · Google
CVE-2023-4353
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 · uneditedHeap buffer overflow in ANGLE in Google Chrome prior to 116.0.5845.96 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
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 confidenceHeap buffer overflow in ANGLE (a graphics abstraction library used by Chrome for WebGL rendering) allows remote attackers to exploit heap corruption via a crafted HTML page, potentially achieving arbitrary code execution.
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
ChromeWeb browser
< 116.0.5845.96
Debian LinuxOperating system
= 11.0= 12.0
FedoraOperating system
= 38CVSS 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.
-
Check Google Chrome versionOpen Chrome, go to chrome://settings/help, or run 'google-chrome --version' in terminalAffected if Version number is lower than 116.0.5845.96
-
Verify ANGLE library presenceThe ANGLE library (libangle*.so) is bundled with Chrome for WebGL; confirm Chrome is installed and functionalAffected if Chrome is installed without the patched version
-
Check Chrome package version on DebianRun 'dpkg -l | grep google-chrome' or 'apt show google-chrome-stable'Affected if Package version shows less than 116.0.5845.96
-
Check Chrome package version on FedoraRun 'rpm -qa | grep chrome' or 'dnf info google-chrome-stable'Affected if Package version shows less than 116.0.5845.96
Your environment is affected if Google Chrome version is below 116.0.5845.96, as the heap buffer overflow exists in the bundled ANGLE library for WebGL rendering.
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 · scoped116.0.5845.96
Update Google Chrome to version 116.0.5845.96 or later to patch the ANGLE heap overflow vulnerability.
Chrome 116.0.5845.96 or later (or corresponding chromium package version provided by your distribution)
- Open Chrome and navigate to Help > About Google Chrome (or go to chrome://version) to check your current version
- If the version is earlier than 116.0.5845.96, click 'Update Google Chrome' if the button is available
- Restart Chrome to complete the update
- Alternatively, on Linux systems, run 'sudo apt update && sudo apt upgrade' (Debian) or 'sudo dnf update' (Fedora) to update the chromium package through the system package manager
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4353 — 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-4353 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