ChromeWeb browser · Google
CVE-2022-0460
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 Window Dialogue in Google Chrome prior to 98.0.4758.80 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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 Google Chrome's Window Dialogue component prior to version 98.0.4758.80. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, potentially leading to heap corruption and 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
< 98.0.4758.80CVSS 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.
-
Verify Google Chrome is installedCheck for Chrome executable: On Windows, look in Program Files/Google/Chrome/Application/ or check for chrome.exe. On Mac, look in /Applications/Google Chrome.app. On Linux, run which google-chrome or which chrome.Affected if Google Chrome browser is installed on the system
-
Determine installed Chrome versionOpen chrome://version in the Chrome address bar and note the version number displayed, or run 'google-chrome --version' (Linux) or 'chrome --version' from command line.Affected if Unable to retrieve version number but Chrome is present
-
Compare version against affected rangeTake the version from step 2 and compare the full version string to 98.0.4758.80. Any version below 98.0.4758.80 (such as 98.0.4758.x, 97.x, 96.x, etc.) is within the affected range.Affected if Installed version is less than 98.0.4758.80 (e.g., 97.0.4692.99, 96.0.4664.93, etc.)
User is affected if Google Chrome is installed and the installed version is lower than 98.0.4758.80, since the use-after-free vulnerability in the Window Dialogue component can be triggered by visiting a crafted HTML page.
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 · scoped98.0.4758.80
Update Google Chrome to version 98.0.4758.80 or later. Organizations should deploy browser updates via patch management systems and notify users of the critical update requirement.
Chrome 98.0.4758.80 or later
- Open Google Chrome browser
- Click on the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click on 'About Google Chrome'
- The browser will automatically check for updates and display the current version
- If an update is available, click 'Update Google Chrome'
- After the update downloads, click 'Relaunch' to restart Chrome and apply the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0460 — 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-0460 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