VDB

CVE-2020-6420

CVE-2020-6420 PUBLISHED

Reported by chrome · Published March 20, 2020

Insufficient policy enforcement in media in Google Chrome prior to 80.0.3987.132 allowed a remote attacker to bypass same origin policy via a crafted HTML page.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
chromiumArch Linux80.0.3987.132-1
ChromeGoogle80.0.3987.132
chromium-browserUbuntu:18.04:LTS80.0.3987.149-0ubuntu0.18.04.1
chromium-browserUbuntu:16.04:LTS80.0.3987.149-0ubuntu0.16.04.1

Affected products

VendorProductVersions
GoogleChromeunspecified
GoogleChrome*
archchromium0

Timeline

  • Mar 5, 2020 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Sep 8, 2025 CVE Updated
  • Jun 2, 2026 Security Advisory (3 in total, the first dated here)
  • Aug 29, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2020-6420
vulnetix vdb fixes CVE-2020-6420

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-6420/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›