SafariWeb browser · Apple
CVE-2016-4666
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.1 is affected. Safari before 10.0.1 is affected. tvOS before 10.0.1 is affected. The issue involves the "WebKit" 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 WebKit allows remote attackers to execute arbitrary code or cause denial of service via crafted malicious web content. The vulnerability stems from improper memory handling in the browser rendering engine, enabling heap-based memory corruption that can be leveraged for code execution.
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.1< 10.1< 10.0.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 Safari version on macOSOpen Safari, click Safari in the menu bar, then select About Safari. The version number is displayed in the window that opens.Affected if The version shown is earlier than 10.0.1
-
Identify the iOS version on iPhone or iPadOpen the Settings app, tap General, then tap About. The iOS version is displayed near the top of the screen.Affected if The version shown is earlier than 10.1 (for example, 10.0.x or any 9.x version)
-
Identify the tvOS version on Apple TVOpen Settings on Apple TV, go to General, then select About. The tvOS version is displayed on this screen.Affected if The version shown is earlier than 10.0.1
-
Confirm JavaScript is enabled in SafariIn Safari, go to Preferences, click the Security tab, and verify that Enable JavaScript is checked. On iOS, go to Settings > Safari > Advanced and ensure JavaScript is turned on.Affected if JavaScript is enabled in the browser settings (this is required for the malicious web content to trigger the vulnerability)
A user is affected if their Safari, iOS, or tvOS version falls below the fixed releases (10.0.1 for Safari and tvOS, 10.1 for iOS) and JavaScript remains enabled in the browser, allowing crafted web content to trigger the memory corruption.
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.0.110.1
Apply vendor-supplied patches by updating iOS to 10.1 or later, Safari to 10.0.1 or later, and tvOS to 10.0.1 or later. Disable JavaScript in Safari settings as an interim workaround if updates cannot be immediately deployed.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4666 — 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-2016-4666 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