CVE-2017-2393
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 is affected. The issue involves the "Safari Reader" component. It allows remote attackers to conduct Universal XSS (UXSS) attacks 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 · moderate confidenceA Universal XSS (UXSS) vulnerability in the Safari Reader component allows remote attackers to execute arbitrary JavaScript in the context of any website a user visits. The attack is triggered when a user navigates to a maliciously crafted website, leveraging the Safari Reader feature to inject malicious scripts that bypass same-origin policies.
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<= 10.2.1CVSS 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.
-
Check installed iOS versionGo to Settings > General > About on the iOS device and note the version number shown next to 'Version'Affected if The version displayed is 10.2.1 or any earlier version (e.g., 10.2, 10.1, 10.0.x)
-
Identify the default web browserGo to Settings > Safari and verify that Safari is set as the default browser, or check if Safari is accessible on the deviceAffected if Safari is the default browser or users have access to Safari on the device
-
Confirm Safari Reader availabilityOpen Safari, navigate to any article webpage, and look for the Reader icon (a series of horizontal lines) in the address barAffected if The Reader icon is visible and tappable in Safari, indicating the Safari Reader feature is present and enabled
-
Verify iOS device model compatibilityConfirm the device is an iPhone (any model running the affected iOS version) by checking Settings > General > About > Model NameAffected if The device is an iPhone running iOS 10.2.1 or earlier
A user is affected if their iPhone runs iOS version 10.2.1 or earlier and they have access to Safari with the Reader feature enabled, as the vulnerability can be triggered by visiting a malicious website that exploits the Safari Reader component.
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 dataUpdate affected iOS devices to version 10.3 or later to receive the Apple patch. Organizations should ensure mobile device management (MDM) policies enforce minimum iOS version requirements.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2393 — 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-2393 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