VDB

CVE-2019-5803

CVE-2019-5803 PUBLISHED

Reported by chrome · Published May 23, 2019

Insufficient policy enforcement in Content Security Policy in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to bypass content security 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
chromegoogle73.0.3683.75
chromium-browserUbuntu:18.04:LTS73.0.3683.75-0ubuntu0.18.04.1

Affected products

VendorProductVersions
GoogleChromeprior to 73.0.3683.75
GoogleChrome73.0.3683.75
archchromium0

Timeline

  • Mar 13, 2019 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Aug 4, 2024 CVE Updated
  • Jun 2, 2026 Security Advisory (4 in total, the first dated here)
  • Sep 9, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2019-5803
vulnetix vdb fixes CVE-2019-5803

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-2019-5803/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 ›