ChromeWeb browser · Google
CVE-2022-0790
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 UI in Google Chrome prior to 99.0.4844.51 allowed a remote attacker who convinced a user to engage in specific user interaction to potentially perform a sandbox escape 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 Cast UI component allows a remote attacker who tricks a user into specific interactions with a crafted HTML page to potentially escape the browser's sandbox, achieving code execution outside the sandboxed environment.
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
< 99.0.4844.51CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 installed Google Chrome versionNavigate to chrome://settings/help in the Chrome browser, or use 'Help > About Google Chrome' menu to display the version informationAffected if The displayed version number is less than 99.0.4844.51
-
Verify Chrome version via command line (Windows)Run 'reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version' in Command Prompt to read the installed version from the registryAffected if The version value returned is lower than 99.0.4844.51
-
Verify Chrome version via command line (macOS)Run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal to display the installed versionAffected if The version output is lower than 99.0.4844.51
-
Verify Chrome version via command line (Linux)Run 'google-chrome --version' or 'chromium --version' in the terminal to display the installed versionAffected if The version output is lower than 99.0.4844.51
The environment is affected if Google Chrome version is lower than 99.0.4844.51, as the use-after-free vulnerability in the Cast UI component exists only in versions prior to this patch.
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 · scoped99.0.4844.51
Update Google Chrome to version 99.0.4844.51 or later to patch the vulnerability. Organizations should prioritize patching through their standard patch management processes.
Chrome 99.0.4844.51 or later
- 1. Open Google Chrome browser
- 2. Click on the three-dot menu in the top-right corner
- 3. Select 'Help' > 'About Google Chrome'
- 4. Chrome will automatically check for updates
- 5. If version 99.0.4844.51 or later is available, click 'Update Google Chrome'
- 6. 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
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0790 — 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-0790 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