CVE-2019-8702
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 · uneditedThis issue was addressed with a new entitlement. This issue is fixed in macOS Mojave 10.14.6, Security Update 2019-004 High Sierra, Security Update 2019-004 Sierra, iOS 12.4, tvOS 12.4. A local user may be able to read a persistent account identifier.
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 local user can read a persistent account identifier due to missing entitlement restrictions in macOS and iOS. The vulnerability was addressed by adding a new entitlement to prevent unauthorized access to persistent account identifiers.
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.4< 10.14.6>= 10.12, < 10.12.6>= 10.13, < 10.13.6= 10.12.6= 10.13.6< 12.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Identify the installed operating systemRun 'sw_vers' on macOS, or check Settings > General > About on iOS/tvOS to determine the OS type and exact version numberAffected if The system is running any variant of macOS, iOS, or tvOS from the affected product list
-
Check macOS version against affected rangesRun 'sw_vers -productVersion' to get the exact macOS version (e.g., 10.13.5, 10.14.5, etc.)Affected if The version is 10.12.x before 10.12.6, 10.13.x before 10.13.6, or any version before 10.14.6
-
Check iOS version against affected rangeCheck Settings > General > About > Version on iOS deviceAffected if The iOS version is earlier than 12.4 (for example, 12.3.x, 11.x, etc.)
-
Check tvOS version against affected rangeCheck Settings > General > About > Version on Apple TVAffected if The tvOS version is earlier than 12.4
A system is affected if it runs any macOS version earlier than 10.14.6 (or earlier than 10.12.6/10.13.6 for older major releases), or any iOS/tvOS version earlier than 12.4, where the missing entitlement allows unauthorized access to persistent account identifiers.
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 · scoped10.12.610.13.610.14.6
Apply the relevant vendor security updates: macOS Mojave 10.14.6, Security Update 2019-004 (High Sierra/Sierra), iOS 12.4, or tvOS 12.4 as appropriate for the affected system.
iOS 12.4, macOS Mojave 10.14.6, Security Update 2019-004 (High Sierra/Sierra), tvOS 12.4
- Back up your device before updating
- For iOS: Go to Settings > General > Software Update and install iOS 12.4
- For macOS: Go to System Preferences > Software Update and upgrade to macOS Mojave 10.14.6, or install Security Update 2019-004 for High Sierra/Sierra
- For tvOS: Go to Settings > System > Software Update and install tvOS 12.4
- Verify the update was successful by checking the OS version in Settings/About
Generated from the published advisory — verify against the referenced sources before acting.
- 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-8702 — 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-8702 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