CVE-2014-4364
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 · uneditedThe 802.1X subsystem in Apple iOS before 8 and Apple TV before 7 does not require strong authentication methods, which allows remote attackers to calculate credentials by offering LEAP authentication from a crafted Wi-Fi AP and then performing a cryptographic attack against the MS-CHAPv1 hash.
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 confidenceThe 802.1X subsystem in Apple iOS before 8 and Apple TV before 7 does not enforce strong authentication methods, allowing a remote attacker operating a malicious Wi-Fi access point to offer LEAP authentication. The captured MS-CHAPv1 hash can then be cracked to recover network credentials.
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.1<= 6.2= 6.0= 6.0.1= 6.0.2= 6.1= 6.1.1= 6.1.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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
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 device typeDetermine if the device is an iOS device (iPhone/iPad) or Apple TVAffected if Device is an Apple iOS device or Apple TV
-
Check iOS versionOn iOS device go to Settings > General > About > Version and note the version numberAffected if iOS version is 7.0 through 7.1.2 (any version below 8.0)
-
Check tvOS versionOn Apple TV go to Settings > General > About > Version and note the version numberAffected if tvOS version is 6.0 through 6.2 (any version below 7.0)
-
Verify 802.1X Wi-Fi configurationCheck if the device is configured for enterprise Wi-Fi authentication (802.1X). On iOS go to Settings > Wi-Fi > tap the connected network > Look for 802.1X credentials or certificate configurationAffected if Device uses 802.1X enterprise Wi-Fi authentication on a vulnerable iOS (< 8.0) or tvOS (< 7.0) version
-
Confirm LEAP authentication option presentInspect the 802.1X network settings or captured authentication negotiation to determine if LEAP is offered as an authentication methodAffected if LEAP authentication is available or negotiated on a vulnerable device version
A defender is affected if they run iOS 7.x on iPhone/iPad or tvOS 6.x on Apple TV and connect to enterprise Wi-Fi networks that may offer LEAP authentication.
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 iOS devices to version 8 or later and Apple TV to version 7 or later, which enforce stronger authentication methods and eliminate the LEAP/MS-CHAPv1 attack vector.
- 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-2014-4364 — 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-4364 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