dbcve.org
ChromeWeb browser · Google

CVE-2020-6454

HIGH · 8.8 CVSS v3.1 Published 2020-04-13
Fix available
A fix is available. Upgrade to 81.0.4044.92 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in extensions in Google Chrome prior to 81.0.4044.92 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted Chrome Extension.

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 confidence

A use-after-free vulnerability in Google Chrome's extension system prior to version 81.0.4044.92 allows a malicious extension to access freed memory, potentially leading to heap corruption and arbitrary code execution.

MitigationUpdate Google Chrome to version 81.0.4044.92 or later. Additionally, enforce policies that restrict extension installation to trusted sources only.

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
Affected:< 81.0.4044.92
FedoraOperating system
Affected:= 30= 31= 32
Debian LinuxOperating system
Affected:= 9.0= 10.0
Backports SleApplication
Affected:= 15.0
LeapOperating system
Affected:= 15.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check your Google Chrome version
    Navigate to chrome://settings/help or run 'google-chrome --version' in terminal
    Affected if Version is lower than 81.0.4044.92 (e.g., 81.0.4044.89 or earlier)
  2. Confirm Chrome is the affected browser
    Verify you are using Google Chrome, not Chromium or other browsers (this CVE affects Chrome specifically)
    Affected if Running Google Chrome with version < 81.0.4044.92
  3. Check if extension system is in use
    Inspect enabled extensions at chrome://extensions or check if any extensions are loaded
    Affected if Any extension is installed and enabled (the vulnerability triggers when a malicious extension accesses freed memory)
  4. Verify Linux distribution package version (if applicable)
    For Fedora: 'rpm -q google-chrome'; For Debian: 'dpkg -l | grep google-chrome'; For openSUSE: 'rpm -q google-chrome'
    Affected if Package version corresponds to Chrome < 81.0.4044.92 on affected Fedora (30/31/32), Debian (9.0/10.0), or openSUSE (15.0/15.1) versions

You are affected if you run Google Chrome version below 81.0.4044.92 with any extension enabled on the affected Linux distributions or as a standalone Chrome installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 81.0.4044.92 or later
Fixed in 81.0.4044.92
Interim mitigation

Update Google Chrome to version 81.0.4044.92 or later. Additionally, enforce policies that restrict extension installation to trusted sources only.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6454 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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