SafariWeb browser · Apple
CVE-2017-7093
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 · uneditedAn issue was discovered in certain Apple products. iOS before 11 is affected. Safari before 11 is affected. iCloud before 7.0 on Windows is affected. iTunes before 12.7 on Windows is affected. tvOS before 11 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 confidenceMemory corruption vulnerability in WebKit allows remote attackers to execute arbitrary code or cause denial of service via a crafted website. Affected products include iOS before 11, Safari before 11, iCloud before 7.0 on Windows, iTunes before 12.7 on Windows, and tvOS before 11.
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
<= 10.1.2<= 10.3.3<= 10.2.2<= 6.9.1<= 12.6.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Safari version on macOS or WindowsOn macOS: open Safari, go to Safari > About Safari. On Windows: open iTunes (which includes Safari), go to Help > About iTunes - or check Programs and Features for Safari version.Affected if Version is 10.1.2 or earlier on macOS/Windows
-
Check iOS version on iPhone or iPadOpen Settings > General > About on the iOS device and look at the Version field.Affected if Version is 10.3.3 or earlier (iOS 10.x before iOS 11)
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TV device.Affected if Version is 10.2.2 or earlier (tvOS 10.x before tvOS 11)
-
Check iTunes version on WindowsOpen iTunes, go to Help > About iTunes, or check the program's version in Programs and Features in Control Panel.Affected if Version is 12.6.2 or earlier
-
Check iCloud for Windows versionOpen iCloud, click the gear icon or menu, select About iCloud, or check the version in Windows Programs and Features.Affected if Version is 6.9.1 or earlier
If any Apple product (Safari, iOS, tvOS, iTunes, or iCloud for Windows) is running a version at or below the affected thresholds listed for CVE-2017-7093, the system is vulnerable to remote code execution via WebKit.
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 dataApply vendor security updates: upgrade iOS devices to iOS 11 or later, Safari to version 11 or later, and ensure Windows systems running iCloud or iTunes are updated to versions 7.0 and 12.7 respectively. Avoid browsing untrusted websites until patches are applied.
Fix this in Safari
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7093 — 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-2017-7093 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