CVE-2019-8612
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 logic issue was addressed with improved state management. This issue is fixed in macOS Mojave 10.14.4, Security Update 2019-002 High Sierra, Security Update 2019-002 Sierra, tvOS 12.3, watchOS 5.2.1, macOS Mojave 10.14.5, Security Update 2019-003 High Sierra, Security Update 2019-003 Sierra, iOS 12.3. An attacker in a privileged network position can modify driver state.
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 confidenceThis is a logic flaw in state management within Apple device drivers. An attacker with privileged network position (meaning they can intercept or manipulate network traffic) can modify driver state. The vulnerability affects multiple Apple operating systems including macOS, iOS, tvOS, and watchOS.
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.12.6, < 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Apple operating systemDetermine which Apple OS is running on the device: iOS (iPhone), macOS (Mac), tvOS (Apple TV), or watchOS (Apple Watch)Affected if The device runs any of the affected Apple operating systems listed below
-
Check the installed iOS versionOn the device, go to Settings > General > About and note the Version number; or use Finder/iTunes for connected iPhonesAffected if The iOS version is lower than 12.3 (for example, 12.2, 12.2.1, 12.2.2, 12.1.x, etc.)
-
Check the installed macOS versionClick the Apple menu > About This Mac; the version appears below the macOS name (for example, 10.14.4, 10.13.6, 10.12.6)Affected if The macOS version is 10.12.6 or higher but lower than 10.14.5 (for example, 10.13.6, 10.14, 10.14.1, 10.14.2, 10.14.3, 10.14.4)
-
Check the installed tvOS versionGo to Settings > General > About on Apple TV; the version is listed next to VersionAffected if The tvOS version is lower than 12.3 (for example, 12.2, 12.1.x, etc.)
-
Check the installed watchOS versionOpen the Watch app on paired iPhone, go to General > About; or open Settings on Apple Watch and navigate to General > AboutAffected if The watchOS version is lower than 5.2.1 (for example, 5.2, 5.1.x, etc.)
The device is affected if it runs any of the affected Apple operating systems (iOS, macOS, tvOS, or watchOS) with a version that falls within the specific vulnerable ranges: iOS/tvOS/watchOS below the noted version thresholds, or macOS between 10.12.6 and 10.14.4 inclusive.
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 relevant security updates (iOS 12.3, macOS Security Update 2019-002/2019-003, tvOS 12.3, watchOS 5.2.1) to patched versions. Limit exposure by controlling network access to devices.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8612 — 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-8612 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