dbcve.org
ChromeWeb browser · Google

CVE-2022-1866

HIGH · 8.8 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to 102.0.5005.61 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 Tablet Mode in Google Chrome on Chrome OS prior to 102.0.5005.61 allowed a remote attacker who convinced a user to engage in specific user interactions 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

A use-after-free vulnerability exists in Google Chrome's Tablet Mode on Chrome OS devices prior to version 102.0.5005.61. The flaw allows a remote attacker who tricks a user into specific interactions to potentially exploit heap corruption, leading to arbitrary code execution or denial of service.

MitigationUpdate Google Chrome on Chrome OS to version 102.0.5005.61 or later to patch the use-after-free vulnerability in Tablet Mode.

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:< 102.0.5005.61

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 the operating system is Chrome OS
    Open a terminal and run 'cat /etc/os-info' or check the system information panel to verify Chrome OS is the operating system.
    Affected if The system is not running Chrome OS - this vulnerability only affects Chrome on Chrome OS devices.
  2. Determine the installed Google Chrome version
    Open Chrome, click the three-dot menu in the top-right, go to Help > About Google Chrome. Alternatively, navigate to chrome://settings/help in the address bar.
    Affected if The displayed version is earlier than 102.0.5005.61 (for example, 101.x.x.x or earlier).
  3. Check if Tablet Mode is enabled on the Chrome OS device
    On Chrome OS, click the system tray area in the bottom-right corner, then click the tablet mode icon or go to Settings > Device > Touchpad and enable Tablet mode. Verify Tablet Mode status in the system quick settings panel.
    Affected if Tablet Mode is currently enabled on the device - the vulnerability specifically exists in Tablet Mode functionality.
  4. Inspect Chrome process list for potential exploitation
    Open a terminal and run 'ps aux | grep -i chrome' to list running Chrome processes. Look for any suspicious or unexpected child processes.
    Affected if Unexpected or suspicious Chrome-related processes are running alongside normal Chrome browser processes, which could indicate active exploitation.

A user is affected if their Chrome OS device runs Google Chrome version earlier than 102.0.5005.61 AND has Tablet Mode enabled, making the use-after-free vulnerability in Tablet Mode exploitable.

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

Update Google Chrome on Chrome OS to version 102.0.5005.61 or later to patch the use-after-free vulnerability in Tablet Mode.

Recommended fix High confidence

Chrome version 102.0.5005.61 or later (on Chrome OS)

  1. 1. Open Google Chrome on the Chrome OS device
  2. 2. Click the three-dot menu in the top-right corner
  3. 3. Navigate to Help > About Google Chrome
  4. 4. The browser will check for updates automatically
  5. 5. If an update is available, download and install version 102.0.5005.61 or later
  6. 6. Restart the browser after the update completes
Caveat Chrome updates typically maintain backward compatibility; minor extension compatibility changes 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
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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