ChromeWeb browser · Google
CVE-2021-21199
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 Aura in Google Chrome on Linux prior to 89.0.4389.114 allowed a remote attacker who had compromised the renderer process 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 confidenceUse-after-free vulnerability in Google Chrome's Aura UI framework on Linux prior to version 89.0.4389.114. A remote attacker who had already compromised the renderer process could exploit heap corruption via a crafted HTML page, potentially leading to arbitrary 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
< 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 if Google Chrome is installed on LinuxRun 'which google-chrome' or 'which chrome' in terminal, or check /usr/bin/google-chromeAffected if google-chrome binary exists on the system
-
Determine installed Chrome versionRun 'google-chrome --version' or 'google-chrome -version' in terminalAffected if version number is lower than 89.0.4389.114 (for example, 89.0.4389.90 or earlier)
-
Verify operating system is LinuxRun 'uname -a' or check /etc/os-releaseAffected if running on Linux (the vulnerability is specific to Chrome on Linux)
-
Check if running a vulnerable Fedora releaseRun 'cat /etc/fedora-release' or 'fedora-release'Affected if Fedora version is 32, 33, or 34 with Chrome installed
The environment is affected if Google Chrome version is lower than 89.0.4389.114 on a Linux system, particularly Fedora 32, 33, or 34.
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
Update Google Chrome for Linux to version 89.0.4389.114 or later. This is a renderer process compromise, so prioritize systems where Chrome is used with elevated trust or access to sensitive resources.
Chrome 89.0.4389.114 or later (Fedora packages should be updated via dnf update)
- Open a terminal and update your package lists: sudo dnf check-update
- Upgrade Chrome to the latest version: sudo dnf update google-chrome-stable
- Restart Chrome after the update completes
- Verify the installed version by navigating to chrome://settings/help or running: google-chrome --version
- Ensure the version is 89.0.4389.114 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21199 — 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-21199 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