dbcve.org
ChromeWeb browser · Google

CVE-2024-0222

HIGH · 8.8 CVSS v3.1 Published 2024-01-04
Fix available
A fix is available. Upgrade to 120.0.6099.199 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
Use after free in ANGLE in Google Chrome prior to 120.0.6099.199 allowed a remote attacker who had compromised the renderer process 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

Use-after-free vulnerability in ANGLE (a graphics library abstraction layer used by Chrome for WebGL) allows a remote attacker who has already compromised the renderer process to potentially exploit heap corruption via a specially crafted HTML page. The vulnerability exists in how ANGLE handles graphics objects, where memory is freed but pointers to that memory are not nullified, leading to use-after-free conditions.

MitigationUpdate Google Chrome to version 120.0.6099.199 or later; for enterprise environments, deploy the update via standard patch management processes and verify completion across all 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:< 120.0.6099.199
FedoraOperating system
Affected:= 38= 39

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 Google Chrome version on Windows or Mac
    Navigate to chrome://settings/help or click Help > About Google Chrome to view the installed version number
    Affected if The displayed version is lower than 120.0.6099.199
  2. Check Google Chrome version on Linux
    Run 'google-chrome --version' or 'google-chrome-stable --version' in the terminal
    Affected if The reported version is lower than 120.0.6099.199
  3. Check Chrome version via package manager on Fedora
    Run 'dnf list installed google-chrome' or 'rpm -q google-chrome-stable' to see the installed package version
    Affected if Chrome is installed and the version is lower than 120.0.6099.199
  4. Verify WebGL is enabled (ANGLE graphics backend)
    Navigate to chrome://gpu in Chrome and look for 'WebGL' under the 'Graphics Feature Status' section - ANGLE is the default WebGL backend on Windows and is enabled by default
    Affected if WebGL shows as enabled or hardware accelerated (the vulnerability only applies when ANGLE processes graphics)

You are affected if you are running Google Chrome (any channel) with version lower than 120.0.6099.199 on Windows, Mac, Linux, or Fedora 38/39, and WebGL is enabled (default).

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.6099.199 or later
Fixed in 120.0.6099.199
Interim mitigation

Update Google Chrome to version 120.0.6099.199 or later; for enterprise environments, deploy the update via standard patch management processes and verify completion across all endpoints.

Recommended fix High confidence

Chrome 120.0.6099.199 or later

  1. Open Chrome and navigate to chrome://settings/help to check the current version
  2. If the version is earlier than 120.0.6099.199, click 'Update Google Chrome' to install the latest version
  3. For Fedora systems, alternatively run 'sudo dnf update google-chrome' to update the package
  4. Restart Chrome 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
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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