ChromeWeb browser · Google
CVE-2022-0469
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 Cast in Google Chrome prior to 98.0.4758.80 allowed a remote attacker who convinced a user to engage in specific interactions 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 confidenceA use-after-free vulnerability exists in the Cast component of Google Chrome versions prior to 98.0.4758.80. The vulnerability allows a remote attacker who tricks a user into performing specific interactions on a maliciously crafted HTML page to potentially exploit heap corruption by accessing freed memory.
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 browser is installedCheck for Chrome executable presence: Windows - C:\Program Files\Google\Chrome\Application\chrome.exe, macOS - /Applications/Google Chrome.app, Linux - /opt/google/chrome/chrome. Alternatively, check installed programs list.Affected if Google Chrome browser exists on the system
-
Determine installed Chrome versionOpen Chrome and navigate to chrome://settings/help, or run command: 'chrome --version' on Windows, 'Google Chrome --version' on macOS/Linux, or check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome\DisplayVersion on Windows.Affected if Installed version number is less than 98.0.4758.80
-
Verify Cast component is present and accessibleCheck for Cast functionality: Look for Cast icon in Chrome toolbar (top right area), navigate to chrome://settings/cast, or verify the ChromeCast extension is available in chrome://extensions.Affected if Cast feature is enabled or accessible in the browser
User is affected if Google Chrome version is below 98.0.4758.80 and the Cast component is present/enabled in the browser.
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 to address this vulnerability. In enterprise environments, deploy the browser update via standard software distribution mechanisms and verify the update has been applied across all affected systems.
Chrome 98.0.4758.80 or later
- Open Chrome and navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for updates
- If version is below 98.0.4758.80, click 'Update Google Chrome' and restart the browser
- Alternatively, download Chrome 98.0.4758.80 or later from the official Google Chrome website
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
- 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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0469 — 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-0469 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