dbcve.org
ChromeWeb browser · Google

CVE-2018-6113

MEDIUM · 6.5 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to 66.0.3359.117 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
Improper handling of pending navigation entries in Navigation in Google Chrome on iOS prior to 66.0.3359.117 allowed a remote attacker to perform domain spoofing 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

This is a domain spoofing vulnerability in Google Chrome for iOS caused by improper handling of pending navigation entries. An attacker could exploit this by crafting a malicious HTML page that tricks the browser into displaying a spoofed URL in the address bar, making users believe they're on a legitimate domain when they're not.

MitigationUpdate Google Chrome for iOS to version 66.0.3359.117 or later to receive the patch for this vulnerability.

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:< 66.0.3359.117
Debian LinuxOperating system
Affected:= 9.0
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/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. Identify the Google Chrome installation
    Locate Google Chrome on your iOS device - this vulnerability specifically affects the iOS version of the browser
    Affected if Google Chrome for iOS is installed
  2. Determine the installed Chrome version
    Open Chrome, tap the three dots menu, go to Settings, then tap Chrome to see the version number. Compare this to 66.0.3359.117
    Affected if The installed version is less than 66.0.3359.117 (for example, 66.0.3359.116 or earlier)
  3. Verify pending navigation can occur
    This vulnerability exploits how Chrome handles pending navigation entries - any webpage the user visits can potentially trigger this behavior
    Affected if The browser can be navigated to a page that initiates a pending navigation (which is standard browser behavior)

You are affected if Google Chrome for iOS is installed and its version is below 66.0.3359.117, allowing a crafted page to spoof the displayed URL in the address bar through pending navigation manipulation.

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

Update Google Chrome for iOS to version 66.0.3359.117 or later to receive the patch for this vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing0.5 h
  • Review / QA0.5 h
2.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-6113 — 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-6113 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