ChromeWeb browser · Google
CVE-2023-4362
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 Mojom IDL in Google Chrome prior to 116.0.5845.96 allowed a remote attacker who had compromised the renderer process and gained control of a WebUI process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
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 vulnerability in Chrome's Mojom IDL (Interface Definition Language for Mojo IPC). An attacker who has already compromised the renderer process and gained control of a WebUI process can trigger heap corruption via a crafted HTML page.
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.0CVSS 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 installed Google Chrome versionNavigate to chrome://version in the browser address bar, or run 'google-chrome --version' from command lineAffected if The displayed version is earlier than 116.0.5845.96
-
Check Chromium package version on DebianRun 'dpkg -l | grep chromium' or 'apt list --installed 2>/dev/null | grep chromium' in terminalAffected if The installed chromium package version is earlier than the fixed version for Debian 11 or 12 (check against package repositories)
-
Verify Chrome is actively runningCheck for running Chrome processes using 'ps aux | grep -i chrome' or Task Manager on WindowsAffected if Chrome is running with a vulnerable version - note that exploitation requires the browser to be active with a compromised renderer process
Your environment is affected if you are running Google Chrome version earlier than 116.0.5845.96 or an unpatched Debian chromium package, and the browser is actively running where a compromised renderer could trigger the flaw.
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. Since the attacker already needs renderer compromise, prioritize keeping browsers updated and limiting renderer-to-WebUI process interaction.
Chrome/Chromium 116.0.5845.96 or later
- For Chrome/Chromium on any platform: Navigate to chrome://settings/help and click 'Update Google Chrome', or download the latest version from google.com/chrome
- For Debian Linux 11 (bullseye) and 12 (bookworm): Run 'sudo apt update && sudo apt upgrade' to apply security updates, or specifically 'sudo apt install chromium' to ensure the latest fixed version is installed
- Verify the installed version by running 'chromium --version' or 'google-chrome --version' and confirm it shows version 116.0.5845.96 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4362 — 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-4362 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