ChromeWeb browser · Google
CVE-2022-1860
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 UI Foundations 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 interaction 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 confidenceUse after free vulnerability in UI Foundations component of Google Chrome on Chrome OS allows a remote attacker who tricks a user into specific interactions to potentially exploit heap corruption, which could lead to arbitrary code execution.
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
< 102.0.5005.61CVSS 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.
-
Check Chrome version on Chrome OSNavigate to chrome://version or go to Settings > About Chrome to view the installed Chrome versionAffected if The displayed version is earlier than 102.0.5005.61 and the operating system is Chrome OS
-
Confirm the Chrome OS platformIn chrome://version, check the OS field - this vulnerability specifically affects Chrome on Chrome OS, not other operating systemsAffected if The OS field shows anything other than Chrome OS (the vulnerability is Chrome OS-specific)
-
Identify user interaction patternsReview browser history and recent sessions for suspicious sites that may have tricked users into specific interactions (the CVE requires user interaction to trigger the vulnerability)Affected if Users visited untrusted websites and were tricked into specific interactions while using Chrome on Chrome OS with a vulnerable version
A user is affected if they are running Google Chrome on Chrome OS with a version earlier than 102.0.5005.61 and were potentially tricked into specific interactions with malicious web content.
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 · scoped102.0.5005.61
Upgrade Chrome/Chrome OS to version 102.0.5005.61 or later to patch the vulnerability.
Chrome 102.0.5005.61 or later (Chrome OS should update to the corresponding Chrome OS release)
- Verify current Chrome version by navigating to Settings > Help > About Google Chrome
- If the version is earlier than 102.0.5005.61, click 'Update Google Chrome' to download and install the latest version
- For Chrome OS devices, ensure the device is connected to the internet and signed into a user account to receive automatic system updates
- After the update installs, restart the Chrome browser to apply the security patch
- Confirm the version now shows 102.0.5005.61 or later
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
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1860 — 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-1860 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