dbcve.org
SafariWeb browser · Apple

CVE-2016-7642

HIGH · 8.8 CVSS v3.0 Published 2017-02-20
Fix available
A fix is available. Upgrade to after 12.5.3 or later.
See remediation →
95/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
An issue was discovered in certain Apple products. iOS before 10.2 is affected. Safari before 10.0.2 is affected. iCloud before 6.1 is affected. iTunes before 12.5.4 is affected. The issue involves the "WebKit" component. It allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) 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 · moderate confidence

A memory corruption vulnerability in WebKit allows remote attackers to execute arbitrary code or cause a denial of service by tricking users into visiting a crafted malicious website. The vulnerability affects Safari, iOS, iCloud, and iTunes prior to their respective patched versions. Successful exploitation gives the attacker code execution within the context of the affected application.

MitigationApply the vendor-supplied patches: update iOS to 10.2 or later, Safari to 10.0.2 or later, iCloud to 6.1 or later, and iTunes to 12.5.4 or later. As a temporary workaround, avoid visiting untrusted or unknown websites.

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
SafariWeb browser
Affected:<= 10.0.1
Iphone OsOperating system
Affected:<= 10.1.1
IcloudApplication
Affected:<= 6.0.1
ItunesApplication
Affected:<= 12.5.3

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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 Safari version
    Open Safari, then go to Safari > About Safari (Mac) or Help > About Safari (Windows). Alternatively, check the version in the App Store or system preferences.
    Affected if Safari version is 10.0.1 or earlier and the browser is used to visit untrusted websites
  2. Check iOS version
    On the iPhone or iPad, go to Settings > General > About and look at the Version field.
    Affected if iOS version is 10.1.1 or earlier and the device is used for web browsing
  3. Check iTunes version
    Open iTunes, then go to Help > About iTunes. The version number is displayed in the dialog window.
    Affected if iTunes version is 12.5.3 or earlier and iTunes is used to browse the iTunes Store or access web content
  4. Check iCloud for Windows version
    Open iCloud for Windows, then click the gear icon and select About iCloud. Alternatively, check the installed program version in Windows Control Panel > Programs and Features.
    Affected if iCloud for Windows version is 6.0.1 or earlier and iCloud web features are accessed
  5. Confirm WebKit usage exposure
    Verify that JavaScript is enabled in Safari settings (Safari > Preferences > Security > Enable JavaScript) or that browsing occurs on the affected iOS device.
    Affected if JavaScript is enabled in Safari or browsing is performed on an unpatched iOS device, making the WebKit vulnerability reachable

You are affected if any of Safari (10.0.1 or earlier), iOS (10.1.1 or earlier), iTunes (12.5.3 or earlier), or iCloud (6.0.1 or earlier) are installed and used for web browsing with JavaScript enabled.

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 12.5.3
Interim mitigation

Apply the vendor-supplied patches: update iOS to 10.2 or later, Safari to 10.0.2 or later, iCloud to 6.1 or later, and iTunes to 12.5.4 or later. As a temporary workaround, avoid visiting untrusted or unknown websites.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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