SafariWeb browser · Apple
CVE-2018-4267
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 · uneditedMultiple memory corruption issues were addressed with improved memory handling. This issue affected versions prior to iOS 11.4.1, tvOS 11.4.1, Safari 11.1.2, iTunes 12.8 for Windows, iCloud for Windows 7.6.
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 WebKit memory corruption vulnerability in Safari, iOS, tvOS, iTunes, and iCloud for Windows allowed remote code execution via malicious web content. The vulnerability involved multiple memory handling flaws that could be exploited to achieve arbitrary 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
< 11.1.2< 11.4.1< 11.4.1< 7.6< 12.8CVSS 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 Safari version on macOS or WindowsOn macOS: Open Safari, click Safari > About Safari. On Windows: Open iTunes, click Help > Check for Updates, or check the version in Programs and Features. Compare the displayed version number to 11.1.2.Affected if Installed version is below 11.1.2 and Safari processes untrusted web content.
-
Check iTunes version on WindowsOpen iTunes and go to Help > About iTunes. The version number appears in theAbout iTunes window. Alternatively, check Programs and Features in Control Panel for the installed iTunes version.Affected if Installed version is below 12.8 and iTunes is used to browse or process web content.
-
Check iCloud for Windows versionOpen the iCloud app on Windows. The version is typically displayed in the app window or accessible via the app's About or Settings menu. Alternatively, check Programs and Features in Control Panel.Affected if Installed version is below 7.6 and iCloud for Windows processes untrusted web content.
-
Check iOS version on iPhone or iPadOpen the Settings app on the iOS device. Tap General > About. The version number is displayed next to Software Version.Affected if Installed iOS version is below 11.4.1 and the device accesses untrusted websites.
-
Check tvOS version on Apple TVOn Apple TV, go to Settings > General > About. The tvOS version is displayed on this screen.Affected if Installed tvOS version is below 11.4.1 and the Apple TV processes web content via apps or Safari.
The environment is affected if any installed product (Safari, iTunes, iCloud for Windows, iOS, or tvOS) has a version below the specified thresholds and processes untrusted web content.
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 data7.611.1.211.4.1
Apply vendor-provided patches by updating to iOS 11.4.1+, tvOS 11.4.1+, Safari 11.1.2+, iTunes 12.8+ for Windows, or iCloud for Windows 7.6+.
Fix this in Safari
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-4267 — 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-4267 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