dbcve.org
ChromeWeb browser · Google

CVE-2022-0102

HIGH · 8.8 CVSS v3.1 Published 2022-02-12
Fix available
A fix is available. Upgrade to 97.0.4692.71 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
Type confusion in V8 in Google Chrome prior to 97.0.4692.71 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 confidence

Type confusion vulnerability in Google Chrome's V8 JavaScript engine allows a remote attacker to exploit heap corruption via a crafted HTML page. The flaw occurs when the engine incorrectly handles object type assumptions, potentially enabling arbitrary code execution.

MitigationUpdate Google Chrome to version 97.0.4692.71 or later to patch the V8 type confusion vulnerability. Organizations should deploy the update through their patch management systems 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:< 97.0.4692.71
FedoraOperating system
Affected:= 34= 35= 36

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. Locate Google Chrome installation
    Search for the Chrome executable. On Linux: 'which google-chrome' or check /usr/bin/google-chrome. On Windows: check 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
    Affected if Chrome executable is not found - the system is not affected because Chrome is not installed
  2. Retrieve installed Chrome version
    Run 'google-chrome --version' on Linux, 'chrome.exe --version' on Windows, or open Chrome and navigate to chrome://settings/help to view the version number
    Affected if Command fails or version cannot be determined - cannot assess vulnerability status
  3. Compare version to CVE threshold
    Compare the installed version number to 97.0.4692.71. Note that versions like 97.0.4692.70, 96.0.4664.x, and earlier are all vulnerable
    Affected if Installed version is less than 97.0.4692.71 - the system IS affected by this CVE
  4. Confirm V8 JavaScript engine is in use
    This is automatic in Google Chrome - the V8 engine handles all JavaScript execution. No manual check needed for standard Chrome installations
    Affected if Using a non-Chrome browser or a Chrome variant that does not use V8 - the system is NOT affected (but this is unlikely for standard Chrome installations)

A system is affected if Google Chrome is installed and the installed version is below 97.0.4692.71.

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

Update Google Chrome to version 97.0.4692.71 or later to patch the V8 type confusion vulnerability. Organizations should deploy the update through their patch management systems and verify completion across all endpoints.

Recommended fix High confidence

Chrome 97.0.4692.71 or later (or equivalent Chrome package version in Fedora repositories)

  1. Update Google Chrome to version 97.0.4692.71 or later by navigating to chrome://settings/help or downloading from https://www.google.com/chrome/
  2. For Fedora systems, run 'sudo dnf update' or 'sudo dnf upgrade' to apply the Chrome security update package for your Fedora version (34, 35, or 36)
  3. Restart the browser after the update completes
  4. Verify the version by navigating to chrome://settings/help - the version should show 97.0.4692.71 or higher

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
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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