ChromeWeb browser · Google
CVE-2021-21197
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 TabStrip in Google Chrome prior to 89.0.4389.114 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 Google Chrome's TabStrip component allows remote code execution through heap corruption. The flaw is triggered by a specially crafted HTML page and affects versions prior to 89.0.4389.114.
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
< 89.0.4389.114
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 versionOpen Chrome and navigate to chrome://version, or run 'google-chrome --version' or 'chromium --version' from the command lineAffected if The displayed version is lower than 89.0.4389.114 (e.g., 89.0.4389.100 or earlier)
-
Verify Chrome version on WindowsOn Windows, open Chrome and click Help > About Google Chrome to view the exact version numberAffected if The version shown is less than 89.0.4389.114
-
Check Chromium version on LinuxRun 'chromium --version' or 'chromium-browser --version' in a terminal to determine the installed versionAffected if The reported version is below 89.0.4389.114
-
Confirm Fedora package version (if applicable)On Fedora systems, run 'rpm -q google-chrome' or check the installed package version using the package managerAffected if The Chrome package version corresponds to an unpatched build earlier than 89.0.4389.114
The environment is affected if Google Chrome or Chromium is installed with a version number less than 89.0.4389.114, as this heap buffer overflow in the TabStrip can be triggered by visiting a malicious webpage.
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 · scoped89.0.4389.114
Upgrade Google Chrome to version 89.0.4389.114 or later to obtain the security patch.
Chrome 89.0.4389.114 or later (stable channel)
- Check the current Chrome version by navigating to chrome://settings/help or running 'google-chrome --version' in terminal
- Update Chrome to version 89.0.4389.114 or later. On Fedora systems, run 'sudo dnf update google-chrome' or 'sudo dnf upgrade google-chrome' to install the patched package
- Verify the update was successful by checking the version again - it should show 89.0.4389.114 or higher
- Restart Chrome to ensure the patched version is fully loaded
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-21197 — 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-21197 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