CVE-2014-1287
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 · uneditedUSB Host in Apple iOS before 7.1 and Apple TV before 6.1 allows physically proximate attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted USB messages.
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 the USB Host stack of Apple iOS before 7.1 and Apple TV before 6.1 allows physically proximate attackers to execute arbitrary code or cause denial of service by sending crafted USB messages that corrupt memory.
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<= 6.0.2= 6.0= 6.0.1<= 7.0.6= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5CVSS 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 your Apple device typeDetermine if the device is an iPhone, iPad, iPod Touch, or Apple TV. On iOS devices, go to Settings > General > About > Model Name. On Apple TV, check the device model.Affected if Device is an Apple TV or iOS device (iPhone/iPad/iPod Touch)
-
Check iOS version on iPhone, iPad, or iPod TouchGo to Settings > General > About > Version to display the installed iOS version.Affected if iOS version is 7.0.6 or lower, or any 7.0.x version (7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6)
-
Check Apple TV versionGo to Settings > General > About to display the installed Apple TV software version.Affected if Apple TV version is 6.0, 6.0.1, or 6.0.2
-
Verify USB connectivity is availableConfirm the device has a Lightning connector (iOS devices) or USB port (Apple TV) that can accept USB connections. The vulnerability is triggered via crafted USB messages sent to the device.Affected if Device supports USB connectivity (required for exploitation)
-
Confirm the device is not updated to patched versionsCompare your installed version against the affected ranges: iOS 7.0 through 7.0.6, or Apple TV 6.0 through 6.0.2. The vulnerability is fixed in iOS 7.1 and Apple TV 6.1 and later.Affected if Device runs a version within the affected ranges and has not been updated to iOS 7.1+ or Apple TV 6.1+
You are affected if your iOS device runs version 7.0 through 7.0.6, or if your Apple TV runs version 6.0 through 6.0.2, and the device has USB connectivity enabled.
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 dataUpdate affected devices to iOS 7.1 or later and Apple TV 6.1 or later; there are no effective workarounds for physical-access attacks of this nature.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1287 — 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-2014-1287 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