CVE-2014-4354
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 · uneditedApple iOS before 8 enables Bluetooth during all upgrade actions, which makes it easier for remote attackers to bypass intended access restrictions via a Bluetooth session.
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 confidenceApple iOS versions prior to 8 automatically enable Bluetooth during all upgrade actions, creating an unintended window where Bluetooth remains active. This allows remote attackers to potentially bypass access restrictions through a Bluetooth session, exploiting the fact that Bluetooth should not be available during the upgrade process.
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.2= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.1= 7.1.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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:A/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check the current iOS versionGo to Settings > General > About on the iOS device and look at the Version field, or use an MDM tool or iTunes to retrieve the iOS version information.Affected if The device is running iOS 7.0 through 7.1.2 (specifically versions 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.1, 7.1.1, or any version <= 7.1.2).
-
Determine if the device performed an upgrade from an affected versionCheck the device's upgrade history through MDM logs, device management software, or by inspecting the iOS restore/upgrade logs if available. Look for any upgrade events that occurred while the device was on an affected iOS version.Affected if The device was upgraded to a newer iOS version while initially running an affected iOS 7.x version listed above.
-
Check current Bluetooth state after a fresh upgradePerform a test upgrade or check the Bluetooth state immediately after an iOS upgrade on a device that was previously on an affected version. Observe whether Bluetooth was automatically enabled without user intervention.Affected if Bluetooth becomes enabled automatically following an upgrade from an affected iOS version, without the user manually turning it on.
A device is affected if it is currently running or was previously upgraded from any iOS version between 7.0 and 7.1.2, as the upgrade process would have automatically enabled Bluetooth during that action.
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 dataUpgrade affected devices to iOS 8 or later, which addresses the Bluetooth enablement issue during upgrades. For enterprise environments, implement Mobile Device Management (MDM) policies to enforce OS updates and control Bluetooth settings.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4354 — 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-4354 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