ChromeWeb browser · Google
CVE-2021-21214
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 Network API in Google Chrome prior to 90.0.4430.72 allowed a remote attacker to potentially exploit heap corruption via a crafted Chrome Extension.
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 Google Chrome's Network API (versions prior to 90.0.4430.72) allows a remote attacker to exploit heap corruption via a maliciously crafted Chrome Extension.
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
< 90.0.4430.72
Debian LinuxOperating system
= 10.0
FedoraOperating system
= 32= 33= 34CVSS 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 installed Chrome versionNavigate to chrome://version in the Chrome browser or run 'google-chrome --version' from command lineAffected if The displayed version is less than 90.0.4430.72 (for example, 89.x.x.x)
-
Check Chrome version on Debian LinuxRun 'dpkg -l | grep google-chrome' or 'apt show google-chrome' if installed via aptAffected if The installed package version is less than 90.0.4430.72~ (the tilde indicates Debian revision)
-
Check Chrome version on Fedora LinuxRun 'rpm -qi google-chrome-stable' if installed via dnf/yumAffected if The installed package version is less than 90.0.4430.72-1 (the -1 indicates Fedora release)
-
Verify Chrome is being usedConfirm the browser in use is Google Chrome and not a Chromium-based alternative (such as Edge, Brave, or Chromium itself), as this CVE specifically targets Google ChromeAffected if The browser is Google Chrome and version is below 90.0.4430.72
You are affected if Google Chrome version is below 90.0.4430.72, or if your Linux distribution package manager shows an installed version from the affected range.
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 · scoped90.0.4430.72
Update Google Chrome to version 90.0.4430.72 or later to apply the security patch.
Chrome 90.0.4430.72 or later
- Check current Chrome version by navigating to chrome://settings/help or running `google-chrome --version` in terminal
- If version is less than 90.0.4430.72, update Chrome to the latest version
- For Debian/Ubuntu: Run `sudo apt-get update && sudo apt-get upgrade google-chrome-stable`
- For Fedora: Run `sudo dnf upgrade google-chrome`
- Restart Chrome browser after applying the update
- Verify the version is now 90.0.4430.72 or higher
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-21214 — 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-21214 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