dbcve.org
SafariWeb browser · Apple

CVE-2017-7052

HIGH · 8.8 CVSS v3.0 Published 2017-07-20
Fix available
A fix is available. Upgrade to 6.2.2 / 10.1.2 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.3.3 is affected. Safari before 10.1.2 is affected. iCloud before 6.2.2 on Windows is affected. iTunes before 12.6.2 on Windows is affected. tvOS before 10.2.2 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 · high confidence

A memory corruption vulnerability in WebKit allows remote attackers to execute arbitrary code or cause denial of service via a crafted website. The vulnerability involves memory corruption that can lead to application crashes or remote code execution when users visit malicious web pages.

MitigationApply available security updates from Apple for iOS (10.3.3+), Safari (10.1.2+), iCloud (6.2.2+), iTunes (12.6.2+), and tvOS (10.2.2+) to patch the WebKit 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
SafariWeb browser
Affected:< 10.1.2
Iphone OsOperating system
Affected:< 10.3.3
TvosOperating system
Affected:< 10.2.2
IcloudApplication
Affected:< 6.2.2
ItunesApplication
Affected:< 12.6.2
WebkitWeb browser
Affected:all versions

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. Identify WebKit-based Apple products in use
    List all Apple software that uses WebKit rendering engine: Safari, iOS, tvOS, iCloud, iTunes. Determine which products are installed in your environment.
    Affected if Any of these products are present and their versions have not been verified.
  2. Check Safari version
    Open Safari, click Safari menu, select About Safari. Compare the version number to 10.1.2 (versions below 10.1.2 are affected).
    Affected if Safari version is below 10.1.2
  3. Check iOS version on iPhone/iPad
    Open Settings > General > About on the iOS device. Note the version number. Compare to 10.3.3 (versions below 10.3.3 are affected).
    Affected if iOS version is below 10.3.3
  4. Check tvOS version on Apple TV
    Open Settings > General > About on Apple TV. Note the version number. Compare to 10.2.2 (versions below 10.2.2 are affected).
    Affected if tvOS version is below 10.2.2
  5. Check iTunes and iCloud versions
    Open iTunes, go to Help > About iTunes. For iCloud on Windows, open iCloud app or check Help > About. Compare iTunes to 12.6.2 and iCloud to 6.2.2.
    Affected if iTunes version is below 12.6.2 or iCloud version is below 6.2.2
  6. Check standalone WebKit version
    If using WebKit as a standalone component (not bundled with Apple products), inspect the WebKit library file or version information. All versions are affected.
    Affected if Any version of standalone WebKit is in use

The environment is affected if any detected product version falls below the fixed thresholds (Safari < 10.1.2, iOS < 10.3.3, tvOS < 10.2.2, iCloud < 6.2.2, iTunes < 12.6.2, or any standalone WebKit).

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 6.2.2 / 10.1.2 / 10.2.2 or later
Fixed in 6.2.210.1.210.2.2
Interim mitigation

Apply available security updates from Apple for iOS (10.3.3+), Safari (10.1.2+), iCloud (6.2.2+), iTunes (12.6.2+), and tvOS (10.2.2+) to patch the WebKit vulnerability.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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