SafariWeb browser · Apple
CVE-2017-7157
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.2 is affected. Safari before 11.0.2 is affected. iCloud before 7.2 on Windows is affected. iTunes before 12.7.2 on Windows is affected. tvOS before 11.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 confidenceA memory corruption vulnerability in WebKit allows remote attackers to execute arbitrary code or cause denial of service by tricking users into visiting crafted malicious websites. The vulnerability affects iOS, Safari, iCloud, iTunes, and tvOS prior to their respective 11.2 or 11.0.2 releases.
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
< 11.0.2< 11.2< 11.2< 7.2< 12.7.2all 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
- 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.
-
Identify installed Apple productsCheck for Safari, iTunes, and iCloud installations on the system. On macOS/Windows, look in Applications folder or use system package managers. For iOS/tvOS, check device settings.Affected if Any of Safari, iTunes, iCloud, or apps using WebKit are installed
-
Check Safari versionOpen Safari, go to Safari > About Safari (macOS) or Settings > Safari > About (iOS). Compare the version number to 11.0.2.Affected if Safari version is less than 11.0.2
-
Check iTunes versionOpen iTunes, go to Help > About iTunes. Compare the version number to 12.7.2.Affected if iTunes version is less than 12.7.2
-
Check iCloud versionOn Windows, open iCloud from system tray or Programs list. On macOS, check System Preferences > iCloud. Compare version to 7.2.Affected if iCloud version is less than 7.2 or if using iCloud for Windows with older version
-
Determine WebKit exposureWebKit is embedded in Safari and other apps. If Safari or any third-party browser using WebKit is present and unpatched, the system is vulnerable. Check which browsers use WebKit (not all browsers do - some use Blink or Gecko).Affected if Any WebKit-based browser is installed with version below the fixed releases
You are affected if any Safari version is below 11.0.2, iTunes below 12.7.2, iCloud below 7.2, or any WebKit-based application is used on unpatched iOS/tvOS versions below 11.2.
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 data7.211.0.211.2
Update all affected Apple products (iOS 11.2+, Safari 11.0.2+, iCloud 7.2+, iTunes 12.7.2+, tvOS 11.2+) to remediate. Users should avoid untrusted websites until patches are applied.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7157 — 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-7157 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