ChromeWeb browser · Google
CVE-2020-6418
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 · uneditedType confusion in V8 in Google Chrome prior to 80.0.3987.122 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 confidenceType confusion vulnerability in Google Chrome's V8 JavaScript engine allows remote attackers to corrupt heap memory via specially crafted HTML pages, potentially enabling arbitrary 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
< 80.0.3987.122
FedoraOperating system
= 30= 31
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
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
- 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.
-
Identify installed Chrome versionOpen chrome://version in the browser or run 'google-chrome --version' or 'chromium --version' from command lineAffected if Version number is less than 80.0.3987.122 (e.g., 79.x, 78.x, etc.)
-
Check Fedora versionRead file /etc/fedora-release or run 'cat /etc/os-release' and look for VERSION_IDAffected if VERSION_ID equals 30 or 31 and Chrome/Chromium is installed
-
Check Red Hat Enterprise Linux versionRead file /etc/redhat-release or run 'cat /etc/os-release' and look for VERSION_ID or the word '6.0'Affected if Version shows 6.0 and Chrome is installed
-
Check Debian versionRead file /etc/debian_version or run 'cat /etc/os-release'Affected if Version shows 9.0 or 10.0 and Chrome/Chromium is installed
User is affected if Google Chrome or Chromium is installed and the browser version is below 80.0.3987.122, or if running the specific Fedora/RHEL/Debian versions listed with Chrome present.
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 · scoped80.0.3987.122
Update Google Chrome to version 80.0.3987.122 or later to patch the V8 type confusion vulnerability.
Chrome 80.0.3987.122 or later
- Update Google Chrome to version 80.0.3987.122 or later
- On Linux systems (Fedora, Debian, Enterprise Linux), use your package manager to update the chromium or google-chrome package: dnf update chromium (Fedora) or apt update && apt upgrade chromium (Debian)
- On Windows or Mac, Chrome should auto-update; alternatively download the latest version from google.com/chrome
- Restart the browser after updating to apply the V8 engine fix
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-2020-6418 — 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-6418 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