CVE-2019-8560
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 · uneditedAn out-of-bounds read was addressed with improved bounds checking. This issue is fixed in iOS 12.3, macOS Mojave 10.14.5, tvOS 12.3, watchOS 5.2.1. A malicious application may be able to read restricted memory.
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 confidenceThis is an out-of-bounds read vulnerability in Apple's iOS, macOS, tvOS, and watchOS. A malicious application could exploit improper bounds checking to read restricted memory beyond allocated buffers, potentially exposing sensitive data. The issue was addressed with improved bounds checking in the specified updates.
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< 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 iOS version on iPhone or iPadGo to Settings > General > About and look at the 'Version' field, or use the 'sw_vers' command in TerminalAffected if The version shown is lower than 12.3 (for example, 12.2, 12.1, etc.)
-
Check macOS versionGo to Apple menu > About This Mac, or use the 'sw_vers' command in TerminalAffected if The version shown is lower than 10.14.5 (for example, 10.14.4, 10.14.3, etc.)
-
Check tvOS version on Apple TVGo to Settings > General > About > Version, or use the 'sw_vers' command if accessible via remote debuggingAffected if The version shown is lower than 12.3
-
Check watchOS version on Apple WatchOpen the Watch app on iPhone, go to General > About, and check the watchOS versionAffected if The version shown is lower than 5.2.1
You are affected if any of your Apple devices (iPhone, iPad, Mac, Apple TV, or Apple Watch) run an OS version lower than 12.3 (iOS/tvOS), 10.14.5 (macOS), or 5.2.1 (watchOS).
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.110.14.512.3
Apply the vendor patches by updating to iOS 12.3 or later, macOS Mojave 10.14.5 or later, tvOS 12.3 or later, and watchOS 5.2.1 or later. In enterprise environments, ensure patch deployment and verify successful installation.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8560 — 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-8560 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