dbcve.org
ChromeWeb browser · Google

CVE-2023-6702

HIGH · 8.8 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 120.0.2210.77 / 120.0.6099.109 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 120.0.6099.109 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 allows a remote attacker to exploit heap corruption via a malicious HTML page. This could enable arbitrary code execution or other security bypasses.

MitigationUpdate Google Chrome to version 120.0.6099.109 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:< 120.0.6099.109
FedoraOperating system
Affected:= 38
Edge ChromiumWeb browser
Affected:< 120.0.2210.77

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. Identify installed Chromium browsers
    Check for Google Chrome or Microsoft Edge installation: On Windows, look in Program Files/Program Files (x86) or run 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName' or 'Get-ItemProperty HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName'. On Linux, check /usr/bin/google-chrome or /usr/bin/microsoft-edge.
    Affected if Either Google Chrome or Microsoft Edge Chromium is installed
  2. Check Google Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help. Note the version number displayed.
    Affected if Version is earlier than 120.0.6099.109
  3. Check Microsoft Edge version
    Open Edge, click the three-dot menu > Help and feedback > About Microsoft Edge, or navigate to edge://settings/help. Note the version number displayed.
    Affected if Version is earlier than 120.0.2210.77
  4. Verify V8 engine is accessible
    Confirm the browser can render HTML pages by visiting any website. The vulnerability is triggered when the V8 JavaScript engine processes a malicious HTML page with specially crafted JavaScript.
    Affected if Browser can render untrusted web content

You are affected if you have Google Chrome version below 120.0.6099.109 or Microsoft Edge Chromium version below 120.0.2210.77 and use the browser to visit web pages.

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 120.0.2210.77 / 120.0.6099.109 or later
Fixed in 120.0.2210.77120.0.6099.109
Interim mitigation

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

Recommended fix High confidence

Chrome 120.0.6099.109 or later / Edge Chromium 120.0.2210.77 or later

  1. Check the current version of Chrome by navigating to chrome://settings/help or Edge by navigating to edge://settings/help
  2. Update Chrome to version 120.0.6099.109 or later through the browser's built-in update mechanism (Menu > Help > About Google Chrome)
  3. Update Edge Chromium to version 120.0.2210.77 or later through the browser's built-in update mechanism (Menu > Help > About Microsoft Edge)
  4. Alternatively, download and install the latest stable version directly from the official Chrome or Edge download pages
  5. Restart the browser after the update completes

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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