ChromeWeb browser · Google
CVE-2014-3187
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 · uneditedGoogle Chrome before 37.0.2062.60 and 38.x before 38.0.2125.59 on iOS does not properly restrict processing of (1) facetime:// and (2) facetime-audio:// URLs, which allows remote attackers to obtain video and audio data from a device 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 confidenceGoogle Chrome on iOS (versions before 37.0.2062.60 and 38.x before 38.0.2125.59) improperly handles facetime:// and facetime-audio:// URL schemes. When a user visits a crafted website, the browser can be triggered to initiate FaceTime calls without proper user consent validation, allowing remote attackers to potentially access the device's video and audio capture capabilities.
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
<= 37.0.2062.59= 37.0.2062.0= 37.0.2062.1= 37.0.2062.2= 37.0.2062.3= 37.0.2062.4= 37.0.2062.5= 37.0.2062.6= 37.0.2062.10= 37.0.2062.11= 37.0.2062.12= 37.0.2062.13all versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome for iOS is installedOn the iOS device, locate the Chrome app icon on the home screen or check via Settings > General > iPhone Storage > Chrome to confirm the app is present.Affected if The app is installed on the device.
-
Determine the installed Chrome for iOS versionOpen Settings on the iOS device, scroll down to Chrome, and tap it. The version number is displayed under the app name.Affected if A Chrome for iOS version is found.
-
Compare the installed version against vulnerable rangesCheck if the installed version matches any of the following: versions <= 37.0.2062.59, any of these specific 37.x versions: 37.0.2062.0 through 37.0.2062.13 (excluding 37.0.2062.7, 37.0.2062.8, 37.0.2062.9 which are not listed as affected), or versions 38.x before 38.0.2125.59.Affected if The installed version falls within any of these vulnerable ranges.
-
Check for FaceTime permission promptsWhen visiting an untrusted website in Chrome for iOS, observe whether the browser automatically launches FaceTime without presenting a clear user consent dialog prompting for camera/microphone permission.Affected if FaceTime initiates without a visible permission dialog after visiting a website with facetime:// or facetime-audio:// links.
A user is affected if Google Chrome for iOS is installed with a version <= 37.0.2062.59, any of the listed 37.0.2062.x versions, or any 38.x version before 38.0.2125.59, allowing websites to trigger FaceTime calls without proper user consent.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Google Chrome for iOS to version 38.0.2125.59 or later. Organizations should inventory iOS devices running vulnerable Chrome versions and push updates via MDM or advise users to update directly from the App Store.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3187 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-3187 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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