LiveActive security incident?Get immediate response
CVE Record

CVE-2020-6418: Type confusion in V8 in Google Chrome prior to 80.0.3987.122 allowed a remote attacker to potentially explo...

Type 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.

HighCVSS 8.8Known exploitedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This Chrome vulnerability can let a malicious web page corrupt memory inside V8, Chrome's JavaScript engine. Because CISA lists CVE-2020-6418 as known exploited, outdated browsers should be treated as urgent exposure, especially on user workstations and unmanaged devices.

Executive priority

Prioritize immediate remediation where outdated Chrome or Chromium remains in use. The combination of high impact, common desktop exposure, and CISA KEV status makes this more urgent than a routine historical browser CVE.

Technical view

CVE-2020-6418 is a V8 type confusion flaw in Google Chrome before 80.0.3987.122. The CVE describes potential heap corruption through a crafted HTML page. CVSS 3.1 is 8.8, with network attack vector, low complexity, no privileges, and user interaction required.

Likely exposure

Systems running Google Chrome before 80.0.3987.122, or distribution Chromium builds covered by the Red Hat, Debian, Gentoo, and Fedora advisories, are the likely exposure. The bundle does not provide a complete affected-version matrix beyond the Chrome fixed release boundary.

Exploitation context

Active exploitation is supported by the CISA KEV listing. The described attack path requires a user to load attacker-crafted HTML content. Public technical write-up references exist, but this assessment does not rely on or provide exploit mechanics.

Researcher notes

The source bundle supports V8 type confusion, heap corruption, user interaction, and the Chrome fixed version. It does not include a complete CPE list or package-version table, so distro-specific validation should follow each vendor advisory.

Mitigation direction

  • Upgrade Chrome to 80.0.3987.122 or later.
  • Apply distro Chromium updates from the cited vendor advisories.
  • Enforce browser auto-update across managed endpoints.
  • Remove or isolate unsupported legacy Chrome or Chromium installations.
  • Check vendor guidance for any embedded Chromium use.

Validation and detection

  • Inventory Chrome and Chromium versions across endpoints.
  • Confirm Chrome reports version 80.0.3987.122 or later.
  • Validate Linux package versions against distro advisories.
  • Review vulnerability scanner findings for CVE-2020-6418.
  • Check browser management telemetry for update failures.
Prepared
Confidence
high
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-843: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-6418 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2020-6418Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChromeunspecifiedListed
Weakness

CWE details

CWE-843

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-843 · source CWE mapping

Access of Resource Using Incompatible Type ('Type Confusion')

Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs