dbcve.org
ChromeWeb browser · Google

CVE-2023-3216

HIGH · 8.8 CVSS v3.1 Published 2023-06-13
Fix available
A fix is available. Upgrade to 114.0.5735.133 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Type confusion in V8 in Google Chrome prior to 114.0.5735.133 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 confidence

Type confusion vulnerability in Chrome's V8 JavaScript engine allows a remote attacker to potentially exploit heap corruption via a crafted malicious HTML page. The vulnerability stems from improper type handling in V8's JIT compilation process.

MitigationUpdate Google Chrome to version 114.0.5735.133 or later. Organizations should deploy browser updates through their patch management systems and verify compliance across endpoints.

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
Affected:< 114.0.5735.133
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 38

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
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 checks

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

  1. Check if Google Chrome is installed
    Open terminal and run: which google-chrome or google-chrome --version. On Windows, check Program Files for Google Chrome folder or look in registry.
    Affected if Google Chrome executable is found on the system
  2. Determine installed Chrome version
    Run: google-chrome --version (Linux/Mac) or check Help > About Google Chrome in the browser. On Windows, you can also run: wmic datafile where name='C:\Program Files\Google\Chrome\Application\chrome.exe' get Version
    Affected if Version number returned is lower than 114.0.5735.133
  3. Check for Chromium on Debian-based systems
    If using Debian 11 or 12, check if chromium package is installed: dpkg -l | grep -i chromium or apt list --installed 2>/dev/null | grep -i chromium
    Affected if Chromium package is installed on Debian 11.0 or 12.0 systems
  4. Check for Chromium on Fedora systems
    If using Fedora 38, check if chromium package is installed: rpm -qa | grep -i chromium or dnf list installed | grep -i chromium
    Affected if Chromium package is installed on Fedora 38

A user is affected if Google Chrome version is installed and is lower than 114.0.5735.133, or if Chromium packages from Debian 11.0, 12.0, or Fedora 38 are present.

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 114.0.5735.133 or later
Fixed in 114.0.5735.133
Interim mitigation

Update Google Chrome to version 114.0.5735.133 or later. Organizations should deploy browser updates through their patch management systems and verify compliance across endpoints.

Recommended fix High confidence

Chrome 114.0.5735.133 or later (or distribution-provided chromium package version that includes the 114.0.5735.133 security fix)

  1. Upgrade Google Chrome to version 114.0.5735.133 or later by navigating to Chrome Menu > Help > About Google Chrome and clicking 'Update' (or manually downloading from google.com/chrome)
  2. For Debian Linux systems, run: sudo apt update && sudo apt upgrade chromium (or chromium-browser package) to receive the security patched version
  3. For Fedora systems, run: sudo dnf update chromium to receive the security patched version
  4. Restart the browser after updating to apply the changes

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

Fix this in Chrome Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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