CVE-2015-5867
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 · uneditedIOHIDFamily in Apple iOS before 9 allows attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via a crafted app.
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 confidenceMemory corruption vulnerability in IOHIDFamily (kernel driver for Human Interface Devices) in iOS versions before 9 allows a crafted malicious app to execute arbitrary code in a privileged kernel context or cause a denial of service through memory corruption.
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<= 8.4.1= 1.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 iOS device typeCheck the device model in Settings > General > About > Model Name to determine if it is an iPhone or Apple WatchAffected if Device is an iPhone or Apple Watch (iPod touch and iPad are not listed as affected products)
-
Check iPhone iOS versionOn the iPhone, go to Settings > General > About > Version to view the installed iOS versionAffected if iOS version displays 8.4.1 or any version lower than 9.0
-
Check Apple Watch watchOS versionOpen the Watch app on the paired iPhone, navigate to My Watch > General > About to view the watchOS versionAffected if watchOS version is exactly 1.0
-
Verify IOHIDFamily driver presenceThe IOHIDFamily kernel extension is built into the iOS kernel and handles Human Interface Devices like the touchscreen and buttons - it cannot be disabled or uninstalled on iOSAffected if The device runs any affected iOS version (the vulnerable driver is always present in the kernel)
Device is affected if it is an iPhone running iOS 8.4.1 or earlier, or an Apple Watch running watchOS 1.0, since the vulnerable IOHIDFamily kernel driver cannot be disabled.
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 · scopedUpdate affected iOS devices to version 9 or later to patch the vulnerability. Deploy via MDM or enterprise mobility management tools to ensure fleet-wide coverage.
iOS 9.0 and later (for Apple Watch: watchOS 2.0 and later)
- Back up your iOS device using iTunes or iCloud before performing the update
- On iPhone or iPad, go to Settings > General > Software Update and download/install iOS 9.0 or later
- For Apple Watch users, update to watchOS 2.0 or later through the Watch app on the paired iPhone (Settings > General > Software Update on the watch)
- After updating, verify the iOS version by going to Settings > General > About and confirming the version is 9.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5867 — 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-2015-5867 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