ChromeWeb browser · Google

CVE-2021-30629

HIGH · 8.8 CVSS v3.1 Published 2021-10-08

Fix available

A fix is available. Upgrade to 93.0.4577.82 or later.

See remediation →

95/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

Use after free in Permissions in Google Chrome prior to 93.0.4577.82 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page.

Technical summary

dbcve analysis · high confidence

Use-after-free vulnerability in the Permissions component of Google Chrome versions prior to 93.0.4577.82. A remote attacker who had already compromised the renderer process could exploit heap corruption via a crafted HTML page.

MitigationUpdate Google Chrome to version 93.0.4577.82 or later. This is a client-side browser vulnerability remedied by standard browser patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 93.0.4577.82

FedoraOperating system

Affected:= 33= 35

CVSS breakdown

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?

dbcve checks

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

Check Google Chrome version on desktop

Navigate to chrome://settings/help or click Help > About Google Chrome to view the installed version number

Affected if The displayed version is lower than 93.0.4577.82 (for example, 93.0.4577.81 or earlier)
Check Chrome version via command line (Windows)

Open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version

Affected if The version value returned is less than 93.0.4577.82
Check Chrome version via command line (Linux)

Run: google-chrome --version or apt list --installed 2>/dev/null | grep google-chrome

Affected if The version displayed is lower than 93.0.4577.82
Check Chrome version on macOS

Run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version or open Chrome and go to Chrome > About Google Chrome

Affected if The version shown is below 93.0.4577.82
Check Fedora package version (if using system package)

Run: rpm -qa | grep -i chrome or dnf list installed | grep -i chrome

Affected if The installed chrome package version is lower than the version bundled in 93.0.4577.82 for Fedora 33 or 35

A user is affected if their installed Google Chrome version is older than 93.0.4577.82, regardless of operating system.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 93.0.4577.82 or later

Fixed in 93.0.4577.82

Interim mitigation

Update Google Chrome to version 93.0.4577.82 or later. This is a client-side browser vulnerability remedied by standard browser patching.

Recommended fix High confidence

Chrome 93.0.4577.82 or later (google-chrome-stable)

For Fedora systems: Run 'sudo dnf check-update' to check for available updates
If google-chrome-stable update is available, run 'sudo dnf update google-chrome-stable' to install the patched version
Alternatively, download the latest Chrome stable from https://www.google.com/chrome/ and install the .rpm package
After installation, ensure Chrome is updated to version 93.0.4577.82 or later by checking About Chrome (three dots > Help > About Google Chrome)
Restart the browser to ensure the patched version is fully loaded

Caveat Chrome updates typically do not introduce breaking changes; however, some older extensions may become incompatible with newer versions

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

5.0 hours of engineering $890

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,424.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2021-30629 — 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

Primary sources

chromereleases.googleblog.comRelease NotesVendor Advisory
crbug.comPermissions RequiredVendor Advisory
lists.fedoraproject.org
lists.fedoraproject.org
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2021-30629?

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.

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

At a glance

A fix existsUpgrade to 93.0.4577.82 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 0.9%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 5 hrs · Low

Typical engagement from $890

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2021-30629 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References