ChromeWeb browser · Google
CVE-2020-6461
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 storage in Google Chrome prior to 81.0.4044.129 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 storage component (Web Storage/IndexedDB) prior to version 81.0.4044.129. A remote attacker with a pre-compromised renderer process can exploit a freed memory object via a crafted HTML page, potentially escaping the sandbox and executing arbitrary code on the host system.
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
< 81.0.4044.129
Debian LinuxOperating system
= 9.0= 10.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
- 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 installed Chrome versionOpen chrome://version in the browser address bar or click Help > About Google ChromeAffected if The displayed version is earlier than 81.0.4044.129
-
Check Chromium version on Debian via dpkgRun command: dpkg -l | grep -i chromiumAffected if The listed chromium or chromium-browser package version is earlier than 81.0.4044.129-1~deb10u1 (or the version string is less than 81.0.4044.129)
-
Check Chromium version on Debian via aptRun command: apt policy chromiumAffected if The installed version shown is earlier than 81.0.4044.129-1~deb10u1
You are affected if you are running Google Chrome or Chromium on Debian versions 9.0/10.0 with a version number lower than 81.0.4044.129.
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 · scoped81.0.4044.129
Update Google Chrome to version 81.0.4044.129 or later. In enterprise environments, test for compatibility with internal web applications before deploying the update organization-wide.
Chrome 81.0.4044.129 or later (Debian: install chromium package version from security updates)
- For Chrome/Chromium browsers: Update to Chrome version 81.0.4044.129 or later by navigating to Chrome menu > Help > About Google Chrome and allowing the update to install, or download the latest stable version from the official Chrome download page
- For Debian Linux systems: Run 'apt update' followed by 'apt upgrade' or 'apt install chromium' to receive the security fix through the package manager
- Restart the 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
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6461 — 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-2020-6461 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