dbcve.org
ChromeWeb browser · Google

CVE-2022-1635

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 Permission Prompts in Google Chrome 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

This is a use-after-free vulnerability in Chrome's Permission Prompts feature. A remote attacker could exploit this by tricking users into specific UI interactions, allowing heap corruption through improper memory handling after a permission prompt object has been freed.

MitigationUpgrade Google Chrome to version 101.0.4951.64 or later to address this vulnerability.

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. Determine installed Google Chrome version
    Open Google Chrome, click the three-dot menu in the top-right, select 'Help', then 'About Google Chrome'. The version number is displayed on that page.
    Affected if the displayed version number is less than 101.0.4951.64 (for example, 101.0.4951.63 or any earlier version)
  2. Confirm Chrome version via command line
    On Windows, run 'chrome --version' in Command Prompt or PowerShell. On macOS, run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal. On Linux, run 'google-chrome --version' or 'chromium --version'.
    Affected if the reported version is earlier than 101.0.4951.64
  3. Check for running Chrome processes
    Open Task Manager (Windows), Activity Monitor (macOS), or use the 'ps' command (Linux) to verify if Google Chrome is currently running.
    Affected if Chrome is running and the installed version meets the affected criteria in step 1 or 2
  4. Review recent Chrome usage for permission prompts
    Inspect browser history or recent activity for sites that may have triggered permission prompts (camera, microphone, location, notifications). This vulnerability is triggered through specific UI interactions with permission dialogs.
    Affected if Chrome has been used to interact with permission prompts and the version is affected

A user is affected if their installed Google Chrome version is earlier than 101.0.4951.64, as this use-after-free flaw exists in all prior versions of the Permission Prompts feature.

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

Upgrade Google Chrome to version 101.0.4951.64 or later to address this vulnerability.

Recommended fix High confidence

Chrome 101.0.4951.64 or later

  1. Open Google Chrome browser
  2. Click on the three-dot menu icon 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 download any available updates
  6. If version 101.0.4951.64 or later is available, click 'Update Google Chrome'
  7. Restart the browser to apply the update

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