SafariWeb browser · Apple
CVE-2019-8558
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 is fixed in iOS 12.2, tvOS 12.2, watchOS 5.2, Safari 12.1, iTunes 12.9.4 for Windows, iCloud for Windows 7.11. Processing maliciously crafted web content may lead to arbitrary code execution.
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 memory corruption vulnerability in WebKit affecting iOS, tvOS, watchOS, Safari, iTunes, and iCloud for Windows. Processing maliciously crafted web content can trigger the memory corruption, potentially allowing arbitrary code execution. The vulnerability is fixed in the stated product versions.
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.1< 7.11< 12.9.4< 12.2< 12.2< 5.2CVSS 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.1/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.
-
Identify the installed Apple productDetermine which Apple product is in use: Safari browser, iOS device, tvOS device, watchOS device, iTunes for Windows, or iCloud for WindowsAffected if Any of the affected products listed in the CVE are in use
-
Check Safari version on macOSOpen Safari, go to Safari menu > About Safari, or run `safari_version` command in TerminalAffected if Version shown is less than 12.1
-
Check iOS version on iPhone/iPadGo to Settings > General > About on the iOS device, or check via iTunes/Finder when device is connectedAffected if iOS version is less than 12.2
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TV deviceAffected if tvOS version is less than 12.2
-
Check watchOS version on Apple WatchOpen Watch app on paired iPhone, go to General > About, or check on Apple Watch via Settings > General > AboutAffected if watchOS version is less than 5.2
-
Check iTunes or iCloud for Windows versionOpen iTunes or iCloud for Windows, go to Help > About iTunes or About iCloud, or check the version in Programs and FeaturesAffected if iTunes version is less than 12.9.4 or iCloud version is less than 7.11
The environment is affected if any of these Apple products are installed and their version falls below the fixed versions (Safari 12.1+, iOS 12.2+, tvOS 12.2+, watchOS 5.2+, iTunes 12.9.4+, iCloud 7.11+).
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.27.1112.1
Apply the security updates for the affected Apple products: iOS 12.2+, tvOS 12.2+, watchOS 5.2+, Safari 12.1+, iTunes 12.9.4+ for Windows, and iCloud 7.11+ for Windows. Prioritize updating mobile devices and browsers that process untrusted web content.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8558 — 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-2019-8558 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