ChromeWeb browser · Google
CVE-2022-0606
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 ANGLE in Google Chrome prior to 98.0.4758.102 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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 the ANGLE graphics library (used by Google Chrome for WebGL rendering) allows a remote attacker to exploit heap corruption via a specially crafted HTML page. The vulnerability exists in Chrome versions prior to 98.0.4758.102.
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
< 98.0.4758.102CVSS 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.
-
Verify Google Chrome is installedCheck for Chrome installation: On Windows, look in C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chrome.Affected if Google Chrome is not installed - the CVE does not apply
-
Determine installed Chrome versionOpen Chrome, click the three-dot menu (top right), select Help, then About Google Chrome. The version number is displayed on this page. Alternatively, navigate to chrome://settings/help in the address bar.Affected if Version shown is less than 98.0.4758.102 - the version is vulnerable
-
Confirm WebGL is enabledNavigate to chrome://settings in the browser, search for 'Hardware acceleration' or visit chrome://gpu to check Graphics Feature Status. WebGL is typically enabled by default for hardware-accelerated graphics rendering.Affected if WebGL is enabled - the ANGLE library is actively used, making exploitation possible; if WebGL is disabled, the attack surface is reduced
A user is affected if Google Chrome is installed with a version prior to 98.0.4758.102 and WebGL hardware acceleration is enabled, as the ANGLE library vulnerability requires active WebGL rendering to be exploitable.
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 · scoped98.0.4758.102
Update Google Chrome to version 98.0.4758.102 or later to patch the vulnerability; organizations should deploy browser updates through their patch management processes.
98.0.4758.102 or later (Chrome version 98 stable release)
- Open Chrome and navigate to Help > About Google Chrome to check the current version
- If the version is less than 98.0.4758.102, click 'Update Google Chrome' to download and install the latest version
- Restart Chrome after the update completes
- Verify the version is now 98.0.4758.102 or later by returning to Help > About Google Chrome
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
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 locallyCheck whether your project pulls in CVE-2022-0606 — 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-2022-0606 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