SafariWeb browser · Apple
CVE-2017-2549
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 10.3.2 is affected. Safari before 10.1.1 is affected. tvOS before 10.2.1 is affected. The issue involves the "WebKit" component. It allows remote attackers to conduct Universal XSS (UXSS) attacks via a crafted web site that improperly interacts with frame loading.
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 Universal XSS (UXSS) vulnerability in WebKit allows remote attackers to bypass the same-origin policy by crafting a website that improperly handles frame loading, enabling execution of arbitrary JavaScript in the context of any website the victim visits.
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<= 10.3.1<= 10.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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the browser in useDetermine if Safari or any WebKit-based browser (like WKWebView-based apps) is being used on the device. On macOS, check the menu bar for Safari. On iOS, look for Safari app. On tvOS, check the Safari app on Apple TV.Affected if The browser is Safari or a WebKit-based browser on Apple platforms.
-
Check Safari version on macOSOpen Safari, click Safari menu, select About Safari. The version number is displayed next to 'Safari'. Compare against 10.1 (affected) and 10.1.1 (fixed).Affected if Safari version is 10.1 or earlier on macOS.
-
Check Safari version on iOSOn iPhone or iPad, go to Settings > Safari. Scroll down and tap About. The version is shown next to Version. Compare against 10.3.1 (affected) and 10.3.2 (fixed).Affected if iOS Safari version is 10.3.1 or earlier.
-
Check tvOS version on Apple TVOn Apple TV, go to Settings > General > About. The tvOS version is displayed. Compare against 10.2 (affected) and 10.2.1 (fixed).Affected if tvOS version is 10.2 or earlier.
-
Verify WebKit version in third-party browsersIf using a third-party browser on iOS (which must use WebKit), check the browser's about or settings page for WebKit version info, or visit a site like browserleaks.com to detect the WebKit version.Affected if The WebKit engine version is earlier than the version bundled in iOS 10.3.2/Safari 10.1.1.
The user is affected if Safari or any WebKit-based browser is running on a device with macOS Safari <= 10.1, iOS Safari <= 10.3.1, or tvOS <= 10.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 dataApply vendor updates: iOS 10.3.2+, Safari 10.1.1+, or tvOS 10.2.1+. This is a client-side browser vulnerability requiring end-user device updates; no server-side configuration can mitigate it.
Fix this in Safari
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2549 — 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-2549 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