dbcve.org
ChromeWeb browser · Google

CVE-2023-4071

HIGH · 8.8 CVSS v3.1 Published 2023-08-03
Fix available
A fix is available. Upgrade to 115.0.5790.170 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
Heap buffer overflow in Visuals in Google Chrome prior to 115.0.5790.170 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

A heap buffer overflow vulnerability exists in the Visuals component of Google Chrome versions prior to 115.0.5790.170. This flaw allows a remote attacker to trigger heap corruption by enticing a user to visit a crafted HTML page, potentially enabling arbitrary code execution or further exploitation.

MitigationUpdate Google Chrome to version 115.0.5790.170 or later. Organizations should deploy the update through their patch management infrastructure and verify successful installation across all affected 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:< 115.0.5790.170

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 installed Google Chrome version
    Open Chrome, click the three-dot menu in the top-right corner, select Help, then select About Google Chrome. The version number is displayed on this page.
    Affected if The displayed version number is lower than 115.0.5790.170 (for example, 115.0.5790.169 or any earlier version).
  2. Check Chrome version via command line (Windows)
    Open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version
    Affected if The version returned is lower than 115.0.5790.170.
  3. Check Chrome version via command line (macOS)
    Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
    Affected if The version returned is lower than 115.0.5790.170.
  4. Check Chrome version via command line (Linux)
    Open Terminal and run: google-chrome --version or chromium --version depending on the package installed
    Affected if The version returned is lower than 115.0.5790.170.

You are affected if Google Chrome version installed on the system is any version prior to 115.0.5790.170, as the heap buffer overflow exists in the Visuals component of those versions.

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

Update Google Chrome to version 115.0.5790.170 or later. Organizations should deploy the update through their patch management infrastructure and verify successful installation across all affected endpoints.

Recommended fix High confidence

Chrome 115.0.5790.170 or later

  1. Open Google Chrome browser
  2. Click on the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click on 'About Google Chrome'
  5. The browser will automatically check for updates and display the current version
  6. If an update is available, click 'Update Google Chrome'
  7. Restart the browser to complete the installation
  8. Verify the version by returning to 'About Google Chrome' - it should show version 115.0.5790.170 or later
Caveat Chrome upgrades are typically seamless; minor extension compatibility issues may occur with older extensions

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
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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