ChromeWeb browser · Google
CVE-2021-30633
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 Indexed DB API in Google Chrome prior to 93.0.4577.82 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 Indexed DB API that allows a remote attacker who has already compromised the renderer process to potentially escape the browser sandbox via a crafted HTML page.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Google Chrome versionNavigate to chrome://settings/help or use the command line: google-chrome --version (Linux) or look at About Google Chrome in the menu (Windows/Mac)Affected if The displayed version is less than 93.0.4577.82
-
Check operating system versionRun 'cat /etc/os-release' on Linux or check System Properties on Windows. On Fedora, run 'fedora-release' or 'cat /etc/fedora-release'Affected if The system is running Fedora 33 or Fedora 35 with an affected Chrome version
-
Verify Indexed DB API presenceThe Indexed DB API is a standard web API built into Chrome and is always enabled by default. No configuration check is needed - it is present in all Chrome installations.Affected if This condition is always true for any Chrome installation, meaning the vulnerability is potentially exploitable if version check shows affected version
You are affected if your Google Chrome version is earlier than 93.0.4577.82, or if you are running Chrome on Fedora 33 or Fedora 35 with an unpatched version.
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 to patch the vulnerability.
Chrome 93.0.4577.82 or later (stable release)
- Check current Chrome version by navigating to chrome://version in the browser address bar
- Update Chrome to version 93.0.4577.82 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome', or by using your system's package manager (e.g., 'sudo dnf update google-chrome-stable' on Fedora)
- Restart Chrome after the update completes
- Verify the version by navigating to chrome://version to confirm the update was successful and version is 93.0.4577.82 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30633 — 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-30633 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