ChromeWeb browser · Google
CVE-2023-6703
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 · uneditedUse after free in Blink 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 confidenceUse-after-free vulnerability in Blink (Google Chrome's rendering engine) allows a remote attacker to exploit heap corruption via a crafted HTML page, potentially leading to arbitrary code execution. The vulnerability affects Chrome versions prior to 120.0.6099.109.
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
< 120.0.6099.109CVSS 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://settings/help in the Chrome address bar, or run 'google-chrome --version' from command lineAffected if The displayed version is lower than 120.0.6099.109 (e.g., 119.x.x.x or earlier)
-
Verify Chrome is runningOpen Task Manager (Ctrl+Shift+Esc) or run 'tasklist | findstr chrome' in command promptAffected if Chrome processes are currently active and the version is vulnerable
-
Check Chrome release channelNavigate to chrome://settings/help and look for the channel indicator (Stable, Beta, Dev, Canary) under the version numberAffected if Channel is Stable, Beta, or Dev and version is below 120.0.6099.109
-
Confirm Blink rendering engine is in useNavigate to chrome://version in the address bar and verify 'Blink' is listed under 'Command Line'Affected if Chrome is using Blink (standard for modern Chrome) and version is vulnerable
You are affected if Google Chrome is running and its version is lower than 120.0.6099.109.
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 · scoped120.0.6099.109
Update Google Chrome to version 120.0.6099.109 or later to patch the vulnerability. Organizations should ensure browser update policies are enforced across endpoints.
120.0.6099.109 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click 'About Google Chrome'
- Chrome will automatically check for updates and display the current version
- If an update is available, click 'Update Google Chrome'
- After the update downloads, click 'Relaunch' to restart Chrome and apply the update
- Alternatively, download the latest Chrome version directly from https://www.google.com/chrome/ and install it
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-6703 — 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-6703 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