dbcve.org
ChromeWeb browser · Google

CVE-2019-5800

MEDIUM · 6.5 CVSS v3.1 Published 2019-05-23
Fix available
A fix is available. Upgrade to 73.0.3683.75 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Insufficient policy enforcement in Blink in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to bypass content security policy 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 confidence

A content security policy (CSP) bypass vulnerability in Google Chrome's Blink rendering engine (versions prior to 73.0.3683.75) allowed remote attackers to bypass CSP restrictions via specially crafted HTML pages, potentially enabling cross-site scripting or data injection attacks.

MitigationUpdate Google Chrome to version 73.0.3683.75 or later. In enterprise environments, deploy browser updates through endpoint management tools and verify compliance across the fleet.

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:< 73.0.3683.75
BackportsOperating system
Affected:= sle-15
LeapOperating system
Affected:= 15.0= 15.1= 42.3

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
None
Integrity
High
Availability
None

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

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 Google Chrome version
    Open chrome://settings/help in the Chrome browser, or run 'google-chrome --version' or 'chrome --version' from command line
    Affected if The displayed version is lower than 73.0.3683.75
  2. Check Chrome package version on OpenSUSE
    Run 'rpm -q google-chrome' or 'dpkg -l google-chrome' to list the installed package version
    Affected if The package version is earlier than 73.0.3683.75
  3. Identify if CSP headers are in use
    Review web application HTTP responses for 'Content-Security-Policy' headers, or check web server configuration files for CSP directives
    Affected if CSP headers are actively deployed - the bypass only affects environments using Content-Security-Policy

You are affected if Google Chrome (or the packaged Chrome on OpenSUSE) is version 73.0.3683.75 or earlier and your environment uses Content-Security-Policy headers.

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 73.0.3683.75 or later
Fixed in 73.0.3683.75
Interim mitigation

Update Google Chrome to version 73.0.3683.75 or later. In enterprise environments, deploy browser updates through endpoint management tools and verify compliance across the fleet.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
5.0 hours of engineering $880
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5800 — 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-2019-5800 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