dbcve.org
ChromeWeb browser · Google

CVE-2022-1633

HIGH · 8.8 CVSS v3.1 Published 2022-07-26
Fix available
A fix is available. Upgrade to 101.0.4951.64 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 Sharesheet in Google Chrome on Chrome OS prior to 101.0.4951.64 allowed a remote attacker who convinced a user to engage in specific UI 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 the Sharesheet component of Google Chrome on Chrome OS before version 101.0.4951.64. The flaw allows a remote attacker to potentially exploit heap corruption by tricking users into performing specific UI interactions, leading to arbitrary code execution possibilities.

MitigationUpdate Google Chrome on Chrome OS to version 101.0.4951.64 or later to patch the use-after-free vulnerability in the Sharesheet component.

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

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. Identify the operating system
    Open Settings > About Chrome OS or visit chrome://version to confirm the OS is Chrome OS
    Affected if The system is not Chrome OS (this CVE specifically affects Chrome OS only)
  2. Check the Chrome browser version
    In Chrome OS, go to Settings > About Chrome or visit chrome://version and note the version number displayed
    Affected if The displayed version is earlier than 101.0.4951.64 (for example, 101.0.4951.0, 100.x.x.x, etc.)
  3. Confirm Chrome version is within the vulnerable range
    Compare your installed version number against the affected range: versions less than 101.0.4951.64 are vulnerable
    Affected if Your Chrome version starts with a number lower than 101, or is 101.0.4951.x where x is less than 64
  4. Verify the Sharesheet component is accessible
    On Chrome OS, access the Sharesheet by selecting a shareable item (image, link, or file) and using the share function in the context menu or app
    Affected if You actively use the Sharesheet feature on Chrome OS, though the vulnerability could potentially be triggered even during casual use

You are affected if you are running Google Chrome on Chrome OS with a version number lower than 101.0.4951.64 and the Sharesheet feature is accessible on your device

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

Update Google Chrome on Chrome OS to version 101.0.4951.64 or later to patch the use-after-free vulnerability in the Sharesheet component.

Recommended fix High confidence

Chrome 101.0.4951.64 or later

  1. 1. Verify current Chrome version by navigating to chrome://settings/help or clicking Help > About Google Chrome
  2. 2. If Chrome version is earlier than 101.0.4951.64, initiate an update by clicking 'Update Google Chrome' (if prompted)
  3. 3. Restart Chrome to complete the update process
  4. 4. For enterprise deployments using managed updates, deploy Chrome version 101.0.4951.64 or later via your organization's software distribution tools
  5. 5. Verify the update was successful by checking chrome://settings/help shows version 101.0.4951.64 or later
Caveat Chrome stable releases rarely introduce breaking changes; however, some extensions or enterprise policies may require re-validation after major version updates

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-1633 — 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-1633 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