dbcve.org
SafariWeb browser · Apple

CVE-2016-4613

MEDIUM · 6.5 CVSS v3.0 Published 2017-02-20
Fix available
A fix is available. Upgrade to after 12.5.1 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
An issue was discovered in certain Apple products. Safari before 10.0.1 is affected. iCloud before 6.0.1 is affected. iTunes before 12.5.2 is affected. tvOS before 10.0.1 is affected. The issue involves the "WebKit" component. It allows remote attackers to obtain sensitive information 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

An information disclosure vulnerability in WebKit allows remote attackers to obtain sensitive information by tricking users into visiting a crafted malicious website. The vulnerability affects Safari, iCloud, iTunes, and tvOS in versions prior to the fixed releases.

MitigationUpdate all affected Apple products to the specified versions or later: Safari 10.0.1, iCloud 6.0.1, iTunes 12.5.2, and tvOS 10.0.1. For enterprise environments, deploy the updates via your patch management system and verify successful installation.

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.0
IcloudApplication
Affected:<= 6.0.0
ItunesApplication
Affected:<= 12.5.1
Apple TvOperating system
Affected:= 10.0.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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 installed Apple products
    Check if Safari, iCloud for Windows, iTunes for Windows, or Apple TV software are installed on your system. For Windows systems, check Add/Remove Programs or the installation directories. For Apple TV, check the system version in Settings.
    Affected if Any of these affected products are present on the system
  2. Check Safari version
    Open Safari, click Safari in the menu bar, then select About Safari. The version number will display next to Safari.
    Affected if Version is 10.0.0 or earlier
  3. Check iCloud for Windows version
    Open the iCloud control panel or check the installed version in Programs and Features. The version typically displays as 6.x.x.
    Affected if Version is 6.0.0 or earlier
  4. Check iTunes version
    Open iTunes, then go to Help > About iTunes. The version number displays in the dialog window.
    Affected if Version is 12.5.1 or earlier
  5. Check tvOS version on Apple TV
    On Apple TV, go to Settings > General > About to view the software version.
    Affected if Version is exactly 10.0.0 (the affected version)
  6. Confirm WebKit usage context
    Recognize that this vulnerability is triggered through WebKit rendering when users visit malicious websites. The affected products all include WebKit components for web content rendering.
    Affected if Users can browse the internet or view web content within any of the affected applications

You are affected if any of these Apple products are installed with versions within the specified ranges and users can access web content through them, making them vulnerable to information disclosure when visiting crafted malicious websites.

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.1
Interim mitigation

Update all affected Apple products to the specified versions or later: Safari 10.0.1, iCloud 6.0.1, iTunes 12.5.2, and tvOS 10.0.1. For enterprise environments, deploy the updates via your patch management system and verify successful installation.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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