dbcve.org
ChromeWeb browser · Google

CVE-2021-30553

HIGH · 8.8 CVSS v3.1 Published 2021-06-15
Fix available
A fix is available. Upgrade to 91.0.4472.101 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in Network service in Google Chrome prior to 91.0.4472.101 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 confidence

Use-after-free vulnerability in Google Chrome's Network service component allows a remote attacker to exploit heap corruption via a crafted HTML page. The flaw exists in the network handling code where memory is freed but pointers are not properly cleared, enabling potential code execution when the freed memory is later accessed.

MitigationUpdate Google Chrome to version 91.0.4472.101 or later to receive the patched version. Organizations should deploy browser updates through their patch management systems and verify completion across endpoints.

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
Affected:< 91.0.4472.101
FedoraOperating system
Affected:= 33= 34

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version on desktop systems
    Open Chrome, click the three-dot menu, go to Help > About Google Chrome. The version number is displayed on this page. Alternatively, run 'google-chrome --version' from command line on Linux.
    Affected if The displayed version number is lower than 91.0.4472.101 (for example, 91.0.4472.99 or earlier)
  2. Check Chrome package version on Fedora Linux
    Open a terminal and run 'dnf list installed google-chrome' or 'rpm -q google-chrome' to see the installed package version.
    Affected if The package version shown is lower than 91.0.4472.101-1 or the package is not listed (not installed)
  3. Verify Chrome is not a bundled or portable version
    Check if the Chrome binary is located in a standard installation path (/usr/bin/google-chrome on Linux, C:\Program Files\Google\Chrome\Application\ on Windows, /Applications/Google Chrome.app on Mac). Non-standard installations may not update automatically.
    Affected if Chrome is installed from an unofficial source or is a portable version that does not receive automatic updates from Google
  4. Confirm the Network service feature is in use
    This vulnerability affects Chrome's Network service component, which is enabled by default in standard Chrome installations. No manual configuration change is needed for this component to be active.
    Affected if Using any standard Chrome build (the Network service cannot be disabled to avoid this issue without using alternate browsers)

You are affected if your installed Google Chrome version is below 91.0.4472.101, regardless of operating system, because the vulnerable Network service code is present in those versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 91.0.4472.101 or later
Fixed in 91.0.4472.101
Interim mitigation

Update Google Chrome to version 91.0.4472.101 or later to receive the patched version. Organizations should deploy browser updates through their patch management systems and verify completion across endpoints.

Recommended fix High confidence

Chrome 91.0.4472.101 or later (stable release)

  1. For Chrome browser: Open Chrome, go to Menu > Help > About Google Chrome, and click 'Update Chrome' to install version 91.0.4472.101 or later
  2. For Fedora systems: Run 'sudo dnf update google-chrome-stable' or 'sudo dnf update' to receive the security patch
  3. Restart the browser after updating
  4. Verify the version by navigating to chrome://settings/help to confirm version 91.0.4472.101 or later is installed

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
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-30553 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-30553 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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