SafariWeb browser · Apple
CVE-2016-4743
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.2 is affected. Safari before 10.0.2 is affected. iCloud before 6.1 is affected. iTunes before 12.5.4 is affected. The issue involves the "WebKit" component. It allows remote attackers to obtain sensitive information from process memory 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 confidenceA WebKit vulnerability allowing remote attackers to either read sensitive information from process memory or cause memory corruption leading to application crashes, via tricking users into visiting specially crafted malicious websites.
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.1<= 6.0.1<= 12.5.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Check Safari version on macOSOpen Safari, click Safari menu > About Safari. Compare the version number to 10.0.1Affected if Version displays 10.0.1 or lower
-
Check iOS version on iPhone/iPadOpen Settings > General > About on the device. Note the Version numberAffected if Version displays 10.1.1 or lower
-
Check iTunes version on Windows or macOSOpen iTunes, click Help > About iTunes. Compare the version number to 12.5.3Affected if Version displays 12.5.3 or lower
-
Check iCloud for Windows versionOpen iCloud in Windows Control Panel or System Preferences on Mac, or check installed programs list. Note the versionAffected if Version displays 6.0.1 or lower
-
Determine WebKit exposureVerify whether the device runs any of the affected Safari, iOS, iCloud, or iTunes versions and is used for web browsingAffected if An affected version is installed AND the browser or web-viewing component is actively used
You are affected if any of these Apple products (Safari, iOS, iCloud, iTunes) are at or below the affected version numbers and are used for web browsing, as the vulnerability is triggerable through visiting malicious websites.
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 dataApply vendor patches by updating affected Apple products (iOS to 10.2+, Safari to 10.0.2+, iCloud to 6.1+, iTunes to 12.5.4+) to remediate the WebKit component vulnerability.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4743 — 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-4743 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