ChromeWeb browser · Google
CVE-2021-30545
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 Extensions in Google Chrome prior to 91.0.4472.101 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 Extensions component. A remote attacker with an already-compromised renderer process could exploit this flaw via a crafted HTML page to achieve heap corruption, 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
< 91.0.4472.101
FedoraOperating system
= 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.
-
Determine installed Chrome versionOpen Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' from command lineAffected if Version is below 91.0.4472.101
-
Verify Chrome channel (if applicable)Navigate to chrome://settings/help and check if the browser reports as 'Stable', 'Beta', 'Dev', or 'Canary' channelAffected if Running a channel version prior to the 91.0.4472.101 stable release
-
Check operating systemRun 'cat /etc/os-release' or 'hostnamectl' to identify the Linux distribution and versionAffected if Running Fedora 33 or Fedora 34 with an affected Chrome version
-
Confirm renderer process exposureThis vulnerability requires a compromised renderer process - assess if the browser is used in an environment where remote content (untrusted HTML pages) is commonly renderedAffected if Users can open untrusted or attacker-controlled HTML pages in Chrome
You are affected if Chrome version is below 91.0.4472.101, regardless of OS, or if running Fedora 33/34 with an unpatched Chrome version in an environment where untrusted HTML content is processed.
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 · scoped91.0.4472.101
Update Google Chrome to version 91.0.4472.101 or later. In enterprise environments, deploy the update via standard patch management processes and verify completion across all affected endpoints.
Chrome 91.0.4472.101 or later (stable release)
- Update Google Chrome to version 91.0.4472.101 or later by visiting chrome://settings/help and clicking 'Update Google Chrome', or download the latest stable version from google.com/chrome
- For Fedora systems, run 'sudo dnf update google-chrome-stable' to apply the security patch
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-30545 — 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-30545 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