ChromeWeb browser · Google
CVE-2021-30632
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 · uneditedOut of bounds write in V8 in Google Chrome prior to 93.0.4577.82 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 confidenceA heap corruption vulnerability exists in the V8 JavaScript engine in Google Chrome versions prior to 93.0.4577.82. The flaw is an out-of-bounds write that can be triggered by a remote attacker via a specially crafted HTML page, potentially allowing the attacker to execute arbitrary code or achieve code execution through heap corruption.
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
< 93.0.4577.82
FedoraOperating system
= 33= 35CVSS 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 Google Chrome versionOpen chrome://version in the Chrome address bar and look at the 'Chrome' line, or run 'google-chrome --version' or 'chromium-browser --version' in a terminalAffected if The version shown is less than 93.0.4577.82
-
Verify the V8 JavaScript engine is in useThis is inherent to Chrome - the V8 engine is Chrome's JavaScript engine and cannot be disabled. No separate check needed.Affected if Chrome is running at all (V8 is always present and active)
-
Check Fedora Linux version if running Chrome on LinuxRun 'cat /etc/fedora-release' or 'fedora-release' in a terminal to identify the Fedora versionAffected if The system is Fedora 33 or Fedora 35 and has Chrome installed
You are affected if you are running any version of Google Chrome prior to 93.0.4577.82 on any OS, or if you are running Chrome on Fedora 33 or Fedora 35 specifically.
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 · scoped93.0.4577.82
Update Google Chrome to version 93.0.4577.82 or later. For enterprise environments, deploy the update via group policy or software distribution tools and verify completion across all endpoints.
Chrome 93.0.4577.82 or later (or equivalent patched version from your browser vendor)
- If using Google Chrome: Navigate to chrome://settings/help and click 'Update Google Chrome', or download and install version 93.0.4577.82 or later from the official Chrome download page
- If using Chromium-based browsers: Check with your browser vendor for the specific update containing the V8 fix
- For Fedora systems: Run 'sudo dnf update google-chrome-stable' or 'sudo dnf update chromium' to apply available security updates
- Restart the browser after updating to ensure the fix is fully applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30632 — 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-30632 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