dbcve.org
ChromeWeb browser · Google

CVE-2023-3420

HIGH · 8.8 CVSS v3.1 Published 2023-06-26
Fix available
A fix is available. Upgrade to 114.0.5735.198 or later.
See remediation →
95/100
Remediation priority · Urgent
High EPSS 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.198 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 Google Chrome's V8 JavaScript engine (versions prior to 114.0.5735.198) allows a remote attacker to exploit heap corruption through a maliciously crafted HTML page, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 114.0.5735.198 or later to patch the V8 type confusion vulnerability.

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.198
Debian LinuxOperating system
Affected:= 11.0= 12.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
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 Chrome version in browser
    Open Chrome and navigate to chrome://version. Look at the 'Version' field near the top of the page.
    Affected if The version number listed is lower than 114.0.5735.198 (for example, 114.0.5735.110 or any earlier version)
  2. Check Chrome version from command line
    Run 'google-chrome --version' or 'chrome --version' in a terminal. On Windows, you can also run '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version'.
    Affected if The output shows a version lower than 114.0.5735.198
  3. Check Chromium version on Debian Linux
    Run 'dpkg -l | grep chromium' or 'apt show chromium' in a terminal to see the installed package version.
    Affected if The installed chromium package version is lower than the version bundled in Chrome 114.0.5735.198 for your Debian release (check package changelog for exact version mapping)

You are affected if your installed Chrome or Chromium browser version is below 114.0.5735.198, as this is the version that patched the V8 type confusion flaw.

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.198 or later
Fixed in 114.0.5735.198
Interim mitigation

Update Google Chrome to version 114.0.5735.198 or later to patch the V8 type confusion vulnerability.

Recommended fix High confidence

Chrome/Chromium version 114.0.5735.198 or later

  1. For Chrome/Chromium browser users: Open the browser, go to Settings > Help > About Chrome, and it will automatically check for and install updates to version 114.0.5735.198 or later
  2. Alternatively, download the latest Chrome stable build from the official Google Chrome release page (chromereleases.googleblog.com)
  3. For Debian Linux users: Run 'sudo apt update && sudo apt upgrade' to receive the security package update for Chromium
  4. For Debian Linux users: Alternatively run 'sudo apt install chromium=114.0.5735.198-1~deb12u1' (or the version available in Debian 12 security repos)
  5. For Debian 11 (bullseye): Run 'sudo apt install chromium=114.0.5735.198-1~deb11u1' if available, or check Debian Security Tracker for the exact fixed version
  6. After updating, restart the browser and verify the version in chrome://settings/help shows 114.0.5735.198 or higher
Caveat No known breaking changes for this security update; minor version updates typically retain user settings and preferences

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

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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