SafariWeb browser · Apple
CVE-2018-4359
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 12, tvOS 12, watchOS 5, Safari 12, iTunes 12.9 for Windows, iCloud for Windows 7.7.
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 confidenceMultiple memory corruption vulnerabilities in Apple products (iOS, tvOS, watchOS, Safari, iTunes for Windows, iCloud for Windows) prior to versions 12/5/12.9/7.7. The issues were addressed through improved memory handling, likely addressing use-after-free or similar memory management flaws.
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
< 12< 12.0< 12< 5.0< 7.7< 12.9CVSS 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 macOSOpen Safari > About Safari (or run 'safariVersion' in Terminal via 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString')Affected if Version is lower than 12.0
-
Check iTunes for Windows versionOpen iTunes > Help > About iTunes, or check 'C:\Program Files\iTunes\iTunes.exe' version propertiesAffected if Version is lower than 12.9
-
Check iCloud for Windows versionOpen iCloud Control Panel > About, or check Programs and Features in Control Panel for installed iCloud versionAffected if Version is lower than 7.7
-
Check iOS version on iPhone or iPadGo to Settings > General > About > Software Version on the iOS deviceAffected if Version is lower than 12.0 (for example, 11.x)
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TV deviceAffected if Version is lower than 12.0
Any installed Apple product (Safari, iTunes for Windows, iCloud for Windows, iOS, tvOS, or watchOS) with a version lower than the fixed releases (12/12.9/7.7/12.0/5.0) is affected by this memory corruption vulnerability.
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 data5.07.712
Apply vendor-supplied updates: upgrade to iOS 12+, tvOS 12+, watchOS 5+, Safari 12+, iTunes 12.9+ for Windows, or iCloud for Windows 7.7+. This is a high-severity vulnerability; prioritize patching for exposed systems.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-4359 — 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-4359 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