ChromeWeb browser · Google
CVE-2022-0806
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 · uneditedData leak in Canvas in Google Chrome prior to 99.0.4844.51 allowed a remote attacker who convinced a user to engage in screen sharing to potentially leak cross-origin data 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 canvas data leak vulnerability in Google Chrome prior to 99.0.4844.51 allows a remote attacker who tricks a user into screen sharing to potentially exfiltrate cross-origin data through a malicious HTML page exploiting the canvas rendering API.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Identify installed Google Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome. Alternatively, run 'chrome://version' in the address bar or check the executable file properties for ChromeBinaryPath.Affected if Version is listed as below 99.0.4844.51 (e.g., 98.x, 97.x, etc.)
-
Confirm browser is Google Chrome (not Chromium or Edge)Verify the installed browser is specifically Google Chrome, not a Chromium-based alternative. Check the application name in Add/Remove Programs or the executable name.Affected if The affected product is Google Chrome specifically, not other Chromium-based browsers.
-
Determine if screen sharing is enabled or usedCheck if the browser has permission to capture screen content. Look for screen sharing extensions, video conferencing apps that use Chrome for WebRTC screen capture, or enterprise policies controlling getDisplayMedia API.Affected if Screen sharing permissions are granted or the getDisplayMedia API is accessible to web content; the vulnerability requires screen sharing to be active.
Your environment is affected if Google Chrome version is below 99.0.4844.51 AND users have the ability to share their screen via 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 · scoped99.0.4844.51
Update Google Chrome to version 99.0.4844.51 or later; for enterprise environments, deploy the browser update via centralized management tools and verify all endpoints have applied the patch.
Chrome 99.0.4844.51 or later (stable channel)
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Alternatively, navigate to chrome://settings/help in the address bar
- Chrome will automatically check for updates and display the current version
- If an update is available, click 'Update Google Chrome'
- Restart the browser to complete the installation
- Verify the version is 99.0.4844.51 or later by returning to the About page
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0806 — 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-0806 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