dbcve.org
ChromeWeb browser · Google

CVE-2018-16072

MEDIUM · 6.5 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to 69.0.3497.81 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
A missing origin check related to HLS manifests in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to bypass same origin 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 missing origin check in Google Chrome's Blink rendering engine allows HLS (HTTP Live Streaming) manifests to be loaded without proper same-origin policy validation. This enables a malicious webpage to potentially access content from other origins that should be protected by the Same-Origin Policy, bypassing a fundamental browser security boundary.

MitigationUpdate Google Chrome to version 69.0.3497.81 or later. For enterprise environments, ensure Chrome auto-updates are enabled or deploy the updated version via standard software distribution mechanisms.

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:< 69.0.3497.81

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 Chrome version in the browser
    Open a new tab and navigate to chrome://version - look for the 'Chrome' line showing the full version number (e.g., 69.0.3497.81)
    Affected if The displayed version is lower than 69.0.3497.81 (e.g., 68.0.3440.106)
  2. Check Chrome version via Help menu
    Click the three-dot menu in the top-right, select Help, then select About Google Chrome - the version is displayed on that page
    Affected if The version shown is less than 69.0.3497.81
  3. Compare your version to the affected range
    If you have the Chrome version number, compare it against the vulnerable range: any version below 69.0.3497.81 is affected
    Affected if Your installed version starts with 69.0.3497.XX where XX is less than 81, or your version begins with a number lower than 69

You are affected if your installed Google Chrome version is below 69.0.3497.81 - update Chrome to resolve this vulnerability.

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

Update Google Chrome to version 69.0.3497.81 or later. For enterprise environments, ensure Chrome auto-updates are enabled or deploy the updated version via standard software distribution mechanisms.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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