SafariWeb browser · Apple
CVE-2018-4474
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 · uneditedA memory consumption issue was addressed with improved memory handling. This issue is fixed in iCloud for Windows 7.7, watchOS 5, Safari 12, iOS 12, iTunes 12.9 for Windows, tvOS 12. Unexpected interaction causes an ASSERT failure.
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 memory consumption vulnerability in multiple Apple products (iCloud for Windows, watchOS, Safari, iOS, iTunes for Windows, tvOS) causes an ASSERT failure due to unexpected interaction. The issue stems from improper memory handling that can be triggered through specific interactions, leading to denial of service via assertion failure.
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< 7.7< 12.9< 12.0< 12< 5.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 versionOn macOS, open Safari and go to Safari > About Safari. On Windows, open iTunes and check Safari version there, or go to Help > About Safari. Alternatively, check the application file info.Affected if Version is earlier than 12.0
-
Check iCloud for Windows versionOpen the iCloud control panel or Settings app in Windows. The version is typically shown in the About or Settings section of the iCloud application.Affected if Version is earlier than 7.7
-
Check iTunes for Windows versionOpen iTunes and go to Help > About iTunes. The version number is displayed in the pop-up window.Affected if Version is earlier than 12.9
-
Check iOS version on deviceOn the iOS device, go to Settings > General > About. The version number is displayed next to 'Version'.Affected if Version is earlier than 12.0
-
Check tvOS version on Apple TVOn Apple TV, go to Settings > General > About. The version number is displayed next to 'Version'.Affected if Version is earlier than 12.0
-
Check watchOS version on Apple WatchOn the paired iPhone, open the Watch app, go to My Watch > General > About. The watchOS version is shown for the connected Apple Watch.Affected if Version is earlier than 5.0
Any installed instance of Safari, iCloud, iTunes, iOS, tvOS, or watchOS with a version number below the respective threshold (12, 7.7, 12.9, 12.0, 12, 5.0) is affected.
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 patches by updating to iCloud for Windows 7.7, watchOS 5, Safari 12, iOS 12, iTunes 12.9 for Windows, or tvOS 12 or later as appropriate for each affected product.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-4474 — 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-4474 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