ChromeWeb browser · Google
CVE-2021-38022
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 · uneditedInappropriate implementation in WebAuthentication in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to 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 confidenceThis vulnerability in Google Chrome's WebAuthentication component prior to version 96.0.4664.45 contains an inappropriate implementation that allows a remote attacker to leak cross-origin data through a crafted HTML page, bypassing the Same-Origin Policy protections.
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
< 96.0.4664.45
FedoraOperating system
= 34
Debian LinuxOperating system
= 10.0= 11.0CVSS 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.
-
Determine installed Chrome versionNavigate to chrome://version in the Chrome browser address bar or go to Help > About Google Chrome. Note the version number displayed.Affected if The version shown is earlier than 96.0.4664.45 (for example, 95.x.x.x or 94.x.x.x).
-
Confirm browser is using WebAuthenticationThis vulnerability affects the WebAuthentication (WebAuthn) API. Check if any web applications on your network use WebAuthn for authentication by reviewing your browser's saved passwords or enterprise configurations.Affected if WebAuthn is actively used and the Chrome version is below 96.0.4664.45.
-
Check Chrome package version on Fedora 34On Fedora 34 systems, run: rpm -q google-chrome-stable and compare the output version against 96.0.4664.45.Affected if The installed google-chrome-stable package version is less than 96.0.4664.45.
Your environment is affected if Google Chrome version is below 96.0.4664.45 and WebAuthentication (WebAuthn) features are in use.
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 · scoped96.0.4664.45
Update Google Chrome to version 96.0.4664.45 or later to address the cross-origin data leakage vulnerability.
Chrome 96.0.4664.45 or later
- Upgrade Google Chrome to version 96.0.4664.45 or later
- On Linux distributions (Fedora 34, Debian 10.0, 11.0), apply system security updates for the chromium or google-chrome packages
- Restart the browser to ensure the security fix is applied
- Verify the installed Chrome version by navigating to chrome://settings/help
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-2021-38022 — 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-38022 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