SafariWeb browser · Apple
CVE-2017-7006
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.3 is affected. Safari before 10.1.2 is affected. tvOS before 10.2.2 is affected. The issue involves the "WebKit" component. It allows remote attackers to conduct a timing side-channel attack to bypass the Same Origin Policy and obtain sensitive information via a crafted web site that uses SVG filters.
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 confidenceThis is a timing side-channel vulnerability in WebKit that allows attackers to bypass the Same Origin Policy. By measuring timing differences in SVG filter processing, attackers can infer information about cross-origin content, enabling data theft from other domains.
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.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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/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 or application in useDetermine if Safari or any application using WebKit is being used. Check the user agent string or application info to confirm WebKit as the rendering engine.Affected if The browser or application relies on WebKit for rendering web content.
-
Check Safari version on macOSOpen Safari, go to Safari menu > About Safari. Compare the version number to 10.1.2.Affected if Safari version is below 10.1.2.
-
Check iOS version on iPhone or iPadGo to Settings > General > About. Look at the Software Version field. Compare to 10.3.3.Affected if iOS version is below 10.3.3.
-
Check tvOS version on Apple TVGo to Settings > General > About. Look at the Software Version field. Compare to 10.2.2.Affected if tvOS version is below 10.2.2.
-
Check WebKit version for embedded usageFor applications bundling WebKit, locate the WebKit library and query its version information, or check the application documentation for the bundled WebKit version.Affected if The bundled WebKit version is any version (the patch was not released for all versions, only specific patched versions were issued).
A user is affected if they are running Safari below 10.1.2, iOS below 10.3.3, tvOS below 10.2.2, or any WebKit-based application that has not incorporated the patched version of 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 data10.1.210.2.210.3.3
Update affected Apple devices to iOS 10.3.3+, Safari 10.1.2+, or tvOS 10.2.2+. For internal applications using WebKit, ensure the bundled WebKit version includes this patch.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7006 — 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-7006 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