SafariWeb browser · Apple
CVE-2017-2405
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. Safari before 10.1 is affected. The issue involves the "WebKit Web Inspector" 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 confidenceMemory corruption vulnerability in the WebKit Web Inspector component allows remote attackers to execute arbitrary code or cause a denial of service via a specially crafted website. The vulnerability affects iOS devices before version 10.3 and Safari browsers before version 10.1.
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.0.3<= 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
- 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 the browser in useConfirm that Apple Safari is the web browser being used. On iOS devices, check that Safari is the default browser.Affected if Safari is the browser in use on an affected platform
-
Check Safari version on macOSOpen Safari, click Safari in the menu bar, then select About Safari. Compare the version number shown to 10.0.3.Affected if Safari version is 10.0.3 or earlier on macOS
-
Check iOS version on iPhone/iPadOpen Settings app, go to General, then About. Look for the Version field and compare the iOS version to 10.2.1.Affected if iOS version is 10.2.1 or earlier on the device
-
Verify Web Inspector usage contextThe vulnerability exists in the Web Inspector component. On macOS, enable Web Inspector via Safari > Preferences > Advanced > Show Develop menu. On iOS, Web Inspector requires a connected Mac with Safari. The flaw is triggered when visiting a specially crafted website with Web Inspector active.Affected if Web Inspector is enabled and the user visits untrusted websites while using an affected Safari/iOS version
A user is affected if they are running Safari 10.0.3 or earlier on macOS, or iOS 10.2.1 or earlier on an iOS device, and they use or enable the Web Inspector component while browsing.
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 devices to iOS 10.3 or later and Safari 10.1 or later to patch the vulnerability. Avoid visiting untrusted websites until updates 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-2405 — 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-2405 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