CVE-2019-8600
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 input validation. 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 maliciously crafted SQL query 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 Apple's SQL database handling components allowed remote attackers to execute arbitrary code via maliciously crafted SQL queries. The vulnerability affected multiple Apple products (iOS, macOS, tvOS, watchOS, iTunes, iCloud for Windows) and was addressed through improved input validation.
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< 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 installed Apple products on the systemCheck for iTunes, iCloud for Windows, or Apple Device Support in installed programs (Windows: Control Panel > Programs and Features, or via PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion)Affected if Any Apple software (iTunes, iCloud for Windows) is installed on a Windows system
-
Check iTunes version on WindowsOpen iTunes, go to Help > About iTunes, or check Program Files\iTunes\iTunes.exe version propertyAffected if iTunes version is lower than 12.9.5
-
Check iCloud for Windows versionOpen iCloud, click the gear icon > About iCloud, or locate iCloud.exe version in Program FilesAffected if iCloud for Windows version is lower than 7.12, or between 10.0 and 10.4 inclusive
-
Check macOS version on Apple computersClick Apple menu > About This Mac, or run 'sw_vers' in TerminalAffected if macOS version is lower than 10.14.5 (Mojave)
-
Check iOS/tvOS/watchOS version on devicesOn iOS: Settings > General > About > Version; on tvOS: Settings > General > About > Version; on Apple Watch: On Watch app on iPhone > General > AboutAffected if iOS is lower than 12.3, tvOS is lower than 12.3, or watchOS is lower than 5.2.1
A system is affected if any Apple product listed above is installed and its version falls within the vulnerable ranges, particularly when processing untrusted SQL input through Apple's database components.
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 · scoped5.2.17.1210.14.5
Apply the available 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 7.12 for Windows. Prioritize internet-facing systems and those processing untrusted SQL input.
iOS 12.3+, macOS Mojave 10.14.5+, tvOS 12.3+, watchOS 5.2.1+, iTunes 12.9.5+, iCloud 7.12+/10.5+
- For iPhone OS (iOS) devices: Go to Settings > General > Software Update and upgrade to iOS 12.3 or later
- For Mac OS X systems: Go to Apple Menu > System Preferences > Software Update and upgrade to macOS Mojave 10.14.5 or later
- For tvOS devices: Go to Settings > System > Software Update and upgrade to tvOS 12.3 or later
- For watchOS devices: On iPhone, open Watch app, go to General > Software Update and upgrade to watchOS 5.2.1 or later
- For iTunes (Windows): Download and install iTunes 12.9.5 or later from apple.com/itunes
- For iCloud for Windows: Download and install iCloud 7.12 or later (or version 10.5+ if using the newer version)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8600 — 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-8600 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