SafariWeb browser · Apple
CVE-2019-8602
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 corruption issue was addressed by removing the vulnerable code. This issue is fixed in iOS 12.3, macOS Mojave 10.14.5, tvOS 12.3, watchOS 5.2.1, iTunes for Windows 12.9.5, iCloud for Windows 7.12. A malicious application may be able to elevate privileges.
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 multiple Apple products (iOS, macOS, tvOS, watchOS, iTunes for Windows, iCloud for Windows) that could allow a malicious local application to elevate privileges to root or system level. The vulnerability was addressed by removing the vulnerable code path.
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.1< 7.12>= 10.0, < 10.4< 12.9.5< 12.3< 10.14.5< 12.3< 5.2.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 macOS versionRun 'sw_vers -productVersion' in Terminal or open System Preferences > About > Read the version number (e.g., 10.14.4)Affected if Version is below 10.14.5
-
Check Safari version on macOSOpen Safari > Safari menu > About Safari, or run 'defaults read /Applications/Safari.app/Contents/Info.plist CFBundleShortVersionString' in TerminalAffected if Version is below 12.1.1
-
Check iOS version on iPhone/iPadOpen Settings > General > About > Version (e.g., 12.2)Affected if Version is below 12.3
-
Check iTunes version on WindowsOpen iTunes > Help > About iTunes, or open Control Panel > Programs and Features > iTunes > Version columnAffected if Version is below 12.9.5
-
Check iCloud for Windows versionOpen Control Panel > Programs and Features > iCloud > Version column, or open iCloud app > click gear icon > AboutAffected if Version is below 7.12, or between 10.0 and 10.4 (exclusive)
-
Check tvOS or watchOS versionOn Apple TV: Settings > General > About > Version. On Apple Watch: Open Watch app on paired iPhone > My Watch > General > AboutAffected if tvOS version is below 12.3, or watchOS version is below 5.2.1
You are affected if any installed Apple product on your system matches a version below its respective threshold 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 data5.2.17.1210.4
Apply the vendor-supplied security updates: iOS 12.3+, macOS Mojave 10.14.5+, tvOS 12.3+, watchOS 5.2.1+, iTunes 12.9.5+ for Windows, and iCloud for Windows 7.12+. Prioritize updates on multi-user systems where local privilege escalation poses greater risk.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8602 — 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-8602 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