dbcve.org
ChromeWeb browser · Google

CVE-2023-4073

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
Out of bounds memory access in ANGLE in Google Chrome on Mac 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

Out of bounds memory access vulnerability in the ANGLE graphics library in Google Chrome on Mac versions prior to 115.0.5790.170 allows remote attackers to exploit heap corruption via a crafted malicious HTML page.

MitigationUpdate Google Chrome to version 115.0.5790.170 or later on all affected Mac systems to remediate this 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:< 115.0.5790.170
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
    On Mac: run 'ls /Applications/Google Chrome.app' or open Chrome and click Chrome > About Google Chrome. On Linux (Debian/Fedora): run 'which google-chrome' or check via package manager
    Affected if Google Chrome is not found on the system
  2. Determine the installed Google Chrome version
    On Mac: click Chrome menu > About Google Chrome. On Linux: run 'google-chrome --version' in terminal. Compare the version number to 115.0.5790.170
    Affected if Version is lower than 115.0.5790.170
  3. Verify the operating system is an affected platform
    Run 'uname -s' or 'sw_vers' on Mac. On Linux, run 'cat /etc/os-release' to check the distribution and version. This CVE affects Mac, Debian 11.0, Debian 12.0, and Fedora 38
    Affected if OS is not Mac, Debian 11.0, Debian 12.0, or Fedora 38 (the vulnerability does not apply to other platforms)
  4. Check Chrome package version on Linux
    On Debian: run 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable'. On Fedora: run 'rpm -q google-chrome' or 'dnf info google-chrome-stable'
    Affected if Package version is not available or is older than 115.0.5790.170

The environment is affected if Google Chrome version is lower than 115.0.5790.170 AND the system is running Mac, Debian 11.0, Debian 12.0, or Fedora 38

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 on all affected Mac systems to remediate this vulnerability.

Recommended fix High confidence

Chrome version 115.0.5790.170 or later; Debian/Fedora package updates to latest Chrome packages

  1. Open Chrome and navigate to Help > About Google Chrome to check current version
  2. If version is below 115.0.5790.170, download the latest stable Chrome from https://www.google.com/chrome/
  3. Install the updated Chrome browser
  4. Restart Chrome and verify the version is 115.0.5790.170 or later via Help > About Google Chrome
  5. For Linux systems (Debian 11/12, Fedora 38), also run system package updates: 'sudo apt update && sudo apt upgrade' (Debian) or 'sudo dnf update' (Fedora) to ensure all Chrome packages and dependencies are updated
Caveat Chrome browser upgrades typically have no breaking changes for end users; minor interface adjustments may occur

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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