CVE-2015-1095
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 8.3, Apple OS X before 10.10.3, and Apple TV before 7.2 allows physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted HID device.
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 confidenceIOHIDFamily in Apple iOS, OS X, and Apple TV contains a memory corruption vulnerability that can be triggered by a physically proximate attacker connecting a crafted HID (Human Interface Device). Successful exploitation allows arbitrary code execution or denial of service.
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.1<= 10.10.2<= 8.2CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/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 Apple product and operating system versionOn macOS, run 'sw_vers' in Terminal. On iOS, go to Settings > General > About > Version. On Apple TV, go to Settings > General > About > Version.Affected if The device runs Apple TV 7.1 or earlier, macOS 10.10.2 or earlier, or iOS 8.2 or earlier.
-
Confirm IOHIDFamily kernel extension presence on macOSRun 'kextstat | grep IOHIDFamily' in Terminal to check if the IOHIDFamily kernel extension is loaded.Affected if The IOHIDFamily extension is loaded and the OS version is in the affected range.
-
Verify HID device support is enabledCheck if HID devices are supported by inspecting system reports or attempting to connect a standard HID device. On macOS, also verify IOKit is running via 'kextstat | grep IOKit'.Affected if HID device support is active and the OS version falls within the vulnerable version range.
-
Check for available security updatesOn macOS, open System Preferences > Software Update to see if updates are available. On iOS, check Settings > General > Software Update. On Apple TV, check Settings > General > Software Update.Affected if A newer OS version with the patch is available but not installed.
The system is affected if it runs Apple TV 7.1 or earlier, macOS 10.10.2 or earlier, or iOS 8.2 or earlier, and the IOHIDFamily component is present and functional.
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 dataApply vendor-supplied patches: update to iOS 8.3+, macOS 10.10.3+, or Apple TV 7.2+. Since physical access is required for exploitation, ensure unauthorized devices cannot be connected to endpoints.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1095 — 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-1095 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