ChromeWeb browser · Google
CVE-2021-30564
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 · uneditedHeap buffer overflow in WebXR in Google Chrome prior to 91.0.4472.164 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 confidenceHeap buffer overflow vulnerability in WebXR (Web Extended Reality) component of Google Chrome prior to version 91.0.4472.164. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially leading to heap corruption and possible 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
< 91.0.4472.164CVSS 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.
-
Determine installed Chrome version on WindowsOpen Chrome, click the three-dot menu, go to Help > About Google Chrome, or right-click chrome.exe in 'C:\Program Files\Google\Chrome\Application\' and select Properties to view the versionAffected if Version number shown is less than 91.0.4472.164
-
Determine installed Chrome version on macOSOpen Chrome, click Chrome menu in the menu bar, select About Google ChromeAffected if Version number shown is less than 91.0.4472.164
-
Determine installed Chrome version on LinuxRun 'google-chrome --version' in terminal or open Chrome and navigate to chrome://settings/helpAffected if Version number shown is less than 91.0.4472.164
-
Confirm WebXR is accessibleCheck if the browser can run WebXR content. In Chrome, navigate to chrome://flags and search for 'WebXR' to see if the feature is enabled or disabled by policy. Users can also test by visiting any webpage that uses WebXR APIAffected if WebXR is enabled or accessible and the Chrome version is below 91.0.4472.164
Environment is affected if Google Chrome version is earlier than 91.0.4472.164 and the browser can execute WebXR content from web pages
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 · scoped91.0.4472.164
Upgrade Google Chrome to version 91.0.4472.164 or later. For enterprise environments, deploy the update via endpoint management tools and verify successful installation.
Chrome 91.0.4472.164 or later
- Open the Chrome browser
- Navigate to Settings by clicking the three-dot menu in the top-right corner and selecting 'Settings'
- Scroll down and click 'About Chrome' in the left sidebar
- Chrome will automatically check for updates; if version 91.0.4472.164 or later is available, click 'Update Google Chrome'
- If no update is available but your version is below 91.0.4472.164, manually download the latest stable version from the official Chrome download page
- After updating, restart the browser to apply the changes
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
- 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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30564 — 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-2021-30564 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