ChromeWeb browser · Google
CVE-2022-0809
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 · uneditedOut of bounds memory access in WebXR in Google Chrome prior to 99.0.4844.51 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 confidenceOut of bounds memory access in Google Chrome's WebXR (Web Extended Reality) component prior to version 99.0.4844.51 allows a remote attacker to corrupt heap memory via a malicious HTML page, potentially achieving 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.
-
Confirm Google Chrome is installedOpen Chrome and navigate to chrome://version, or check for Chrome in Programs files (Windows) or Applications (Mac/Linux)Affected if Google Chrome browser is present on the system
-
Check installed Chrome versionIn Chrome address bar, go to chrome://version and note the version number displayed, or use command line: chrome --version (Linux) or check About Google Chrome in menuAffected if The displayed version is less than 99.0.4844.51
-
Verify WebXR feature statusIn Chrome, go to chrome://flags and search for 'WebXR' or 'Extended Reality' to see if the WebXR features are enabled or if there are any experimental XR settingsAffected if WebXR features are enabled or set to Default/Enabled (the vulnerability is in the WebXR component)
-
Check if user browses untrusted web contentReview typical browsing habits - determine if the user visits unknown or potentially malicious websites, as exploitation requires viewing a specially crafted HTML pageAffected if User browses arbitrary websites without caution
A user is affected if they run Google Chrome version below 99.0.4844.51 with WebXR features enabled and browse untrusted web content that could contain malicious WebXR exploit code.
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. This is a client-side browser vulnerability with no server-side remediation required.
99.0.4844.51
- Open Chrome and navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for updates
- If an update is available, click 'Update Google Chrome'
- Restart Chrome to complete the update
- Verify the version by navigating to chrome://settings/help and confirm the version is 99.0.4844.51 or later
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
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-0809 — 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-0809 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