SafariWeb browser · Apple
CVE-2019-8562
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 with improved validation. This issue is fixed in iOS 12.2, tvOS 12.2, Safari 12.1, iTunes 12.9.4 for Windows. A sandboxed process may be able to circumvent sandbox restrictions.
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 confidenceMemory corruption vulnerability in sandboxed processes within Apple ecosystem products (iOS, tvOS, Safari, iTunes) that allows sandbox escape and privilege escalation. The fix involved improved validation of memory operations.
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< 12.9.4< 12.2< 12.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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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, then go to Safari > About Safari (or press Cmd+, and look at the version number)Affected if The displayed version is earlier than 12.1
-
Check iTunes version on WindowsOpen iTunes, then go to Help > About iTunes and note the version number shownAffected if The displayed version is earlier than 12.9.4
-
Check iOS version on iPhone or iPadOpen Settings > General > About and look at the iOS version fieldAffected if The version shown is earlier than 12.2
-
Check tvOS version on Apple TVOpen Settings > General > About on the Apple TV deviceAffected if The tvOS version shown is earlier than 12.2
A user is affected if any of their Apple ecosystem products (Safari, iTunes, iOS, or tvOS) are running a version below the fixed releases (12.1, 12.9.4, or 12.2 respectively).
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.
dbcve · scoped12.112.212.9.4
Apply available security updates: iOS 12.2, tvOS 12.2, Safari 12.1, or iTunes 12.9.4 for Windows. This is a critical patch as it enables sandboxed applications to escape security boundaries.
Safari 12.1+, iTunes 12.9.4+, iOS 12.2+, tvOS 12.2+
- Identify which Apple product(s) are affected (Safari, iTunes on Windows, iOS, or tvOS)
- Check the current version of the affected product in its settings or about section
- For Safari: Upgrade to version 12.1 or later
- For iTunes (Windows): Upgrade to version 12.9.4 or later
- For iOS devices: Upgrade to version 12.2 or later
- For Apple TV: Upgrade to tvOS 12.2 or later
- After upgrade, verify the new version in the product's settings or about section
Generated from the published advisory — verify against the referenced sources before acting.
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-2019-8562 — 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-8562 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