CVE-2019-7286
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.1.4, macOS Mojave 10.14.3 Supplemental Update. An application may be able to gain elevated privileges.
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 iOS and macOS allowed a local application to gain elevated privileges by exploiting insufficient input validation. The flaw was patched in iOS 12.1.4 and macOS Mojave 10.14.3 Supplemental Update.
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.1.4< 10.14.3CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 the operating systemCheck if the device runs Apple iOS or macOS. On iOS, look for the Settings app and iPhone/iPad interface. On macOS, look for the Finder-based desktop environment.Affected if The device is running either iOS or macOS
-
Check iOS versionOn iOS, go to Settings > General > About and read the Version field. Note the full version number displayed (for example, 12.1.3 or 12.2).Affected if The iOS version is lower than 12.1.4 (for example, 12.1.3, 12.1.0, or any 12.x version below 12.1.4)
-
Check macOS versionOn macOS, click the Apple menu in the top-left corner and select About This Mac. Read the version number displayed (for example, 10.14.2 or 10.14.3).Affected if The macOS version is lower than 10.14.3 (for example, 10.14.2, 10.14.1, 10.14.0, or any 10.14.x version below 10.14.3)
The system is affected if it runs iOS version lower than 12.1.4 or macOS version lower than 10.14.3.
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.14.312.1.4
Apply the vendor-supplied patches by updating iOS devices to version 12.1.4 or later and macOS systems to 10.14.3 or later.
iOS 12.1.4 or later; macOS Mojave 10.14.3 Supplemental Update or later
- For iOS devices: Navigate to Settings > General > Software Update and install iOS 12.1.4 or later
- For Mac devices: Open System Preferences > Software Update and install macOS Mojave 10.14.3 Supplemental Update or later
- Alternatively, for iOS, connect device to computer and update via iTunes/Finder
- After updating, verify the version in Settings > General > About (iOS) or System Preferences > About (macOS)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7286 — 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-7286 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