dbcve.org
ChromeWeb browser · Google

CVE-2016-1707

MEDIUM · 6.5 CVSS v3.0 Published 2016-07-23
Fix available
A fix is available. Upgrade to after 51.0.2704.106 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
ios/web/web_state/ui/crw_web_controller.mm in Google Chrome before 52.0.2743.82 on iOS does not ensure that an invalid URL is replaced with the about:blank URL, which allows remote attackers to spoof the URL display via a crafted web site.

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

In Google Chrome for iOS before version 52.0.2743.82, the CRWWebController component fails to validate and replace invalid URLs with about:blank. This allows remote attackers to craft malicious web pages that display a spoofed URL in the browser's address bar, potentially facilitating phishing attacks.

MitigationUpdate Google Chrome for iOS to version 52.0.2743.82 or later. If building a custom iOS webview/browser component, implement proper URL validation to replace invalid URLs with about:blank before display.

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:<= 51.0.2704.106

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 application
    Confirm you are using Google Chrome for iOS specifically, not Chrome on Android, Windows, macOS, or another browser. Check the app name in the iOS App Store or installed apps list.
    Affected if The application is not Google Chrome for iOS (the vulnerability only affects the iOS version)
  2. Check installed version
    Open Google Chrome for iOS, tap the three-dot menu, go to Settings, and scroll to the bottom where the version number is displayed. Alternatively, check in iOS Settings > Chrome.
    Affected if Version number cannot be determined or is not visible
  3. Compare against affected range
    Compare your installed version number to 51.0.2704.106. Versions 51.0.2704.106 and below are affected; version 52.0.2743.82 and above are fixed.
    Affected if Installed version is 51.0.2704.106 or lower (for example, 51.0.2704.104, 51.0.2704.100, etc.)

You are affected if you are running Google Chrome for iOS version 51.0.2704.106 or any earlier version.

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 a release after 51.0.2704.106
Interim mitigation

Update Google Chrome for iOS to version 52.0.2743.82 or later. If building a custom iOS webview/browser component, implement proper URL validation to replace invalid URLs with about:blank before display.

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-2016-1707 — 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-2016-1707 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