ChromeWeb browser · Google
CVE-2022-0808
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 Chrome OS Shell in Google Chrome on Chrome OS prior to 99.0.4844.51 allowed a remote attacker who convinced a user to engage in a series of user interaction to potentially exploit heap corruption via 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 confidenceUse-after-free vulnerability in Chrome OS Shell component of Google Chrome on Chrome OS versions prior to 99.0.4844.51. A remote attacker could exploit heap corruption by tricking users into a series of interactions that trigger the use-after-free condition, potentially leading to 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
< 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
- 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.
-
Check Chrome version on Chrome OSNavigate to chrome://version on Chrome OS or go to Settings > About Chrome in the Chrome browser to view the installed version numberAffected if The displayed version is earlier than 99.0.4844.51
-
Confirm the operating system is Chrome OSVerify the device is running Chrome OS. This vulnerability only affects Google Chrome when it runs on Chrome OS, not on other operating systemsAffected if The browser is Google Chrome on Chrome OS and the version is below 99.0.4844.51
-
Verify the Shell component is in useThe vulnerability exists in the Chrome OS Shell component. This component is active during normal Chrome OS desktop interactions including the launcher, shelf, and system UI elementsAffected if Running Chrome on Chrome OS with the Shell component active (standard Chrome OS desktop environment)
A user is affected if they are running Google Chrome on Chrome OS with a version number lower than 99.0.4844.51, where the Chrome OS Shell component is active during normal desktop usage.
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 on Chrome OS to version 99.0.4844.51 or later to patch the vulnerability.
Chrome 99.0.4844.51 or later
- Open Google Chrome on Chrome OS
- Navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for updates and begin downloading version 99.0.4844.51 or later
- After the update completes, restart the Chrome browser to apply the fix
- Verify the version by returning to About Google Chrome and confirming the version is 99.0.4844.51 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0808 — 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-0808 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