SafariWeb browser · Apple
CVE-2017-7059
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 · uneditedA DOMParser XSS issue was discovered in certain Apple products. iOS before 10.3.3 is affected. Safari before 10.1.2 is affected. tvOS before 10.2.2 is affected. The issue involves the "WebKit" component.
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 confidenceA DOMParser Cross-Site Scripting (XSS) vulnerability in WebKit allows attackers to inject malicious scripts through improper parsing of HTML/XML content. This affects iOS devices, Safari browsers, and tvOS devices by exploiting the DOMParser API to execute unauthorized JavaScript in the context of the victim's session.
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.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 Apple product running WebKitDetermine if the device runs Safari (macOS), iOS (iPhone/iPad), or tvOS (Apple TV). On macOS, open Safari > Safari menu > About Safari. On iOS, go to Settings > General > About. On tvOS, go to Settings > General > About.Affected if The device runs Safari, iOS, or tvOS with WebKit.
-
Check Safari browser version on macOSOpen Safari, click Safari menu, select About Safari. Note the version number displayed (e.g., 10.1.1).Affected if Safari version is earlier than 10.1.2.
-
Check iOS version on iPhone or iPadOpen Settings > General > About. Note the version number (e.g., 10.3.2).Affected if iOS version is earlier than 10.3.3.
-
Check tvOS version on Apple TVOpen Settings > General > About. Note the version number (e.g., 10.2.1).Affected if tvOS version is earlier than 10.2.2.
-
Confirm WebKit DOMParser is in useThis vulnerability exploits the DOMParser API in WebKit. If the Safari, iOS, or tvOS version is below the patched thresholds, the vulnerable DOMParser implementation is present.Affected if Any website or web application using DOMParser to parse untrusted HTML/XML content will be processed by the vulnerable WebKit engine.
A user is affected if their Safari browser is below version 10.1.2, their iOS device is below version 10.3.3, or their tvOS device is below version 10.2.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 data10.1.210.2.210.3.3
Update all affected Apple devices to iOS 10.3.3+, Safari 10.1.2+, or tvOS 10.2.2+ to patch the DOMParser XSS vulnerability in WebKit.
Fix this in Safari
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7059 — 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-7059 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