dbcve.org
ChromeWeb browser · Google

CVE-2022-0310

HIGH · 8.8 CVSS v3.1 Published 2022-02-12
Fix available
A fix is available. Upgrade to 97.0.4692.99 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 Task Manager in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via specific user interactions.

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

Heap buffer overflow in Google Chrome's Task Manager component allows a remote attacker to corrupt heap memory through specific user interactions, potentially leading to arbitrary code execution. The vulnerability exists in versions prior to 97.0.4692.99 and is triggered when a user performs certain actions within the Task Manager interface.

MitigationUpdate Google Chrome to version 97.0.4692.99 or later to patch the heap buffer overflow vulnerability. Organizations should deploy the update via their patch management processes and verify successful installation on 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:< 97.0.4692.99

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. Confirm Google Chrome installation
    Check for the presence of Google Chrome on the system. On Windows, look for chrome.exe in Program Files or Program Files (x86). On macOS, check /Applications/Google Chrome.app. On Linux, run 'which google-chrome' or check /usr/bin/google-chrome.
    Affected if Google Chrome is not found on the system.
  2. Identify installed Chrome version
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' from command line. The version number displays in the About Chrome section.
    Affected if The installed version is less than 97.0.4692.99.
  3. Verify Task Manager accessibility
    In Chrome, open the Task Manager by pressing Shift+Escape or clicking the menu (three dots) > More tools > Task Manager. Confirm the Task Manager window launches and displays running processes/extensions.
    Affected if The Task Manager feature is enabled and accessible to the user.
  4. Check Chrome channel (if applicable)
    For enterprise deployments, check the Chrome channel via registry or policy: Windows HKLM\Software\Google\Chrome\BLBeacon or run 'google-chrome --product-version' to confirm the exact build.
    Affected if The installed version is a stable release below 97.0.4692.99.

A user is affected if Google Chrome version 97.0.4692.99 or higher is not installed and the Task Manager feature is accessible on their system.

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.99 or later
Fixed in 97.0.4692.99
Interim mitigation

Update Google Chrome to version 97.0.4692.99 or later to patch the heap buffer overflow vulnerability. Organizations should deploy the update via their patch management processes and verify successful installation on affected endpoints.

Recommended fix High confidence

Chrome 97.0.4692.99 or later

  1. Open Google Chrome browser
  2. Click on the three-dot menu (More options) in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click on 'About Google Chrome'
  5. Chrome will automatically check for and install any available updates
  6. If version is below 97.0.4692.99, restart the browser to complete the update
  7. Alternatively, download the latest Chrome version directly from the official Google Chrome website

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-2022-0310 — 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-0310 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