ChromeWeb browser · Google
CVE-2021-21213
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 WebMIDI in Google Chrome prior to 90.0.4430.72 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 use-after-free vulnerability in the WebMIDI API in Google Chrome versions prior to 90.0.4430.72 allows a remote attacker to potentially exploit heap corruption through a specially crafted HTML page. The vulnerability occurs when the browser continues to reference memory that has already been freed, leading to unpredictable behavior and potential remote 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
< 90.0.4430.72
Debian LinuxOperating system
= 10.0
FedoraOperating system
= 32= 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.
-
Check installed Google Chrome versionOpen chrome://settings/help or run 'google-chrome --version' / 'chrome --version' in terminalAffected if Version is less than 90.0.4430.72
-
Check Chrome package version on DebianRun 'dpkg -l | grep google-chrome' or 'apt show google-chrome-stable'Affected if Package version is less than 90.0.4430.72-1
-
Check Chrome package version on FedoraRun 'rpm -qa | grep chrome' or 'dnf info google-chrome-stable'Affected if Package version is less than 90.0.4430.72-1
-
Verify WebMIDI API accessibilityThe vulnerability is triggered when a specially crafted HTML page accesses the WebMIDI API. Check if Chrome is used in an environment where untrusted web content can be loadedAffected if Chrome versions prior to 90.0.4430.72 are in use and web content can be loaded
You are affected if Google Chrome version is below 90.0.4430.72 and the browser can load untrusted web content that could access the WebMIDI API.
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 · scoped90.0.4430.72
Update Google Chrome to version 90.0.4430.72 or later. Alternatively, disable the WebMIDI API via Chrome policies until the update can be deployed.
Chrome 90.0.4430.72 or later (stable release)
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version is earlier than 90.0.4430.72, click 'Update Google Chrome' to upgrade to the latest version
- Restart the Chrome browser after the update completes
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
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-21213 — 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-21213 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