ChromeWeb browser · Google
CVE-2021-37992
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 read in WebAudio in Google Chrome prior to 95.0.4638.54 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 confidenceOut of bounds read vulnerability in Google Chrome's WebAudio component prior to version 95.0.4638.54 allows a remote attacker to exploit heap corruption through a maliciously 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
< 95.0.4638.54
Debian LinuxOperating system
= 10.0= 11.0CVSS 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, go to Settings > About Chrome, or navigate to chrome://settings/help. Alternatively, run 'google-chrome --version' or 'chromium --version' in terminal.Affected if Version is earlier than 95.0.4638.54 (e.g., 94.x.x.x, 93.x.x.x, etc.)
-
Confirm WebAudio is in useThe WebAudio API is a core browser feature enabled by default in Chrome. No manual configuration check needed - any page using audio context triggers this component.Affected if WebAudio feature is accessible (default state in Chrome)
-
Identify Linux distribution for Debian usersRun 'cat /etc/os-release' or 'lsb_release -a' to identify the Debian version.Affected if System runs Debian 10.0 or Debian 11.0 with Chrome version below 95.0.4638.54
You are affected if Google Chrome (or Chromium-based browsers) version is below 95.0.4638.54, particularly on Debian Linux 10.0 or 11.0 systems.
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 · scoped95.0.4638.54
Update Google Chrome to version 95.0.4638.54 or later. Organizations should push browser updates via patch management to ensure all clients are patched.
Chrome 95.0.4638.54 or later (Debian: install chromium package security updates)
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version is below 95.0.4638.54, click 'Update Google Chrome' to download and install the latest version
- Restart Chrome to complete the update
- For Debian Linux systems, run 'apt update && apt upgrade' or 'apt update && apt install chromium' to receive the security patch
- Verify the update was successful by revisiting chrome://settings/help and confirming version 95.0.4638.54 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
- 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-37992 — 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-37992 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