SafariWeb browser · Apple
CVE-2018-4201
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 11.4 is affected. Safari before 11.1.1 is affected. iCloud before 7.5 on Windows is affected. iTunes before 12.7.5 on Windows is affected. tvOS before 11.4 is affected. watchOS before 4.3.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 · moderate confidenceMemory corruption vulnerability in WebKit allows remote attackers to execute arbitrary code or cause denial of service via a crafted malicious website. The vulnerability affects Safari, iOS, tvOS, watchOS, iCloud for Windows, and iTunes for Windows.
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
< 11.1.1< 11.4< 11.4< 4.3.1< 7.5< 12.7.5CVSS 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.
-
Check if Safari is installed and its versionOpen Safari, go to Safari menu > About Safari. The version number is displayed in the window that opens.Affected if Version shown is earlier than 11.1.1
-
Check iOS version on iPhone or iPadOpen Settings app, tap General > About. The iOS version is displayed next to 'Version'.Affected if Version shown is earlier than 11.4 (for example, 11.3.x or below)
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TV device.Affected if Version shown is earlier than 11.4
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to General > About. The watchOS version appears under the watch name.Affected if Version shown is earlier than 4.3.1
-
Check iCloud for Windows versionOpen iCloud for Windows, click the menu or gear icon, then click About iCloud. The version is displayed in the window that opens.Affected if Version shown is earlier than 7.5
-
Check iTunes for Windows versionOpen iTunes, go to Help > About iTunes. The version number appears in the window that opens.Affected if Version shown is earlier than 12.7.5
You are affected if any of the installed Apple products (Safari, iOS, tvOS, watchOS, iCloud for Windows, or iTunes for Windows) have versions below the minimum fixed versions listed above.
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 data4.3.17.511.1.1
Apply vendor-supplied security updates: update iOS to 11.4+, tvOS to 11.4+, watchOS to 4.3.1+, Safari to 11.1.1+, iCloud for Windows to 7.5+, and iTunes for Windows to 12.7.5+. Avoid untrusted websites as an interim measure.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-4201 — 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-2018-4201 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