dbcve.org
ChromeWeb browser · Google

CVE-2018-17472

CRITICAL · 9.6 CVSS v3.0 Published 2018-11-14
Fix available
A fix is available. Upgrade to 70.0.3538.67 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Incorrect handling of googlechrome:// URL scheme on iOS in Intents in Google Chrome prior to 70.0.3538.67 allowed a remote attacker to escape the <iframe> sandbox 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 URL scheme handler vulnerability in Google Chrome on iOS allows attackers to escape iframe sandbox restrictions via crafted HTML pages that improperly handle the googlechrome:// URL scheme. This client-side vulnerability affects Chrome versions prior to 70.0.3538.67 and requires user interaction with malicious content.

MitigationUpdate Google Chrome for iOS to version 70.0.3538.67 or later to remediate this vulnerability. Users should be advised to update their browser through the App Store.

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:< 70.0.3538.67
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
Debian LinuxOperating system
Affected:= 9.0

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
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 if Google Chrome for iOS is installed
    Open the Settings app on the iOS device, scroll to find Google Chrome in the list of installed apps, or look for the Chrome icon on the home screen
    Affected if Google Chrome for iOS is present on the device
  2. Determine the installed Chrome for iOS version
    Open Chrome app, tap the three-dot menu, go to Settings, then scroll to the bottom to find the version number displayed under 'Chrome'
    Affected if The displayed version number is lower than 70.0.3538.67
  3. Verify iframe sandbox configuration exposure
    Examine whether the browser handles googlechrome:// URL scheme - this requires testing with a crafted HTML page containing an iframe with sandbox attributes that attempts to navigate via the googlechrome:// scheme
    Affected if The iframe sandbox can be escaped by a malicious page using the googlechrome:// URL scheme, allowing navigation outside the sandbox

A user is affected if they have Google Chrome for iOS installed with a version lower than 70.0.3538.67 and encounter malicious content that exploits the iframe sandbox escape via the googlechrome:// URL scheme.

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.

dbcve · scoped
Upgrade available Upgrade to 70.0.3538.67 or later
Fixed in 70.0.3538.67
Interim mitigation

Update Google Chrome for iOS to version 70.0.3538.67 or later to remediate this vulnerability. Users should be advised to update their browser through the App Store.

Recommended fix High confidence

Chrome 70.0.3538.67 or later

  1. Check current Chrome version by navigating to chrome://settings/help or chrome://version
  2. Update Chrome to version 70.0.3538.67 or later using the browser's built-in update mechanism or your system's package manager (e.g., yum, dnf, apt-get)
  3. Restart Chrome after the update completes to apply the changes
  4. Verify the installed version is 70.0.3538.67 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.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-17472 — 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-17472 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