ChromeWeb browser · Google
CVE-2021-21230
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 · uneditedType confusion in V8 in Google Chrome prior to 90.0.4430.93 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 confidenceType confusion vulnerability in V8 JavaScript engine in Google Chrome prior to version 90.0.4430.93 allows a remote attacker to execute arbitrary code via a crafted HTML page by exploiting heap corruption through improper type handling.
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.93
FedoraOperating system
= 32= 33= 34
Debian LinuxOperating system
= 10.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
- 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 Google Chrome version on Windows, macOS, or LinuxOpen Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help, or run 'google-chrome --version' in terminalAffected if The displayed version is earlier than 90.0.4430.93 (e.g., 89.x.x.x or earlier)
-
Check Google Chrome package version on FedoraRun 'rpm -q google-chrome' or 'dnf list installed google-chrome' in terminalAffected if The installed version is less than 90.0.4430.93 (note: Fedora 32, 33, and 34 shipped vulnerable versions)
-
Check Google Chrome package version on DebianRun 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable' in terminalAffected if The installed version is less than 90.0.4430.93 (Debian 10.0 shipped vulnerable versions)
-
Verify Chromium-based browsers are updatedIf using other Chromium-based browsers (Microsoft Edge, Brave, etc.), check their version in the same way and verify the underlying Chromium version matches 90.0.4430.93 or laterAffected if The browser is based on Chromium and its version is earlier than the fixed release
You are affected if Google Chrome or a Chromium-based browser on your system is version 90.0.4430.93 or earlier, particularly on Fedora 32/33/34 or Debian 10.0 systems.
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.93
Update Google Chrome to version 90.0.4430.93 or later to remediate this vulnerability.
Chrome 90.0.4430.93 or later; Chromium-based browsers should update to corresponding fixed releases
- Update Google Chrome to version 90.0.4430.93 or later
- On Linux distributions (Fedora, Debian), update via system package manager: `sudo dnf update` (Fedora) or `sudo apt update && sudo apt upgrade` (Debian)
- Restart the browser after updating
- Verify the version by navigating to chrome://settings/help to confirm the installed version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21230 — 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-21230 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