CVE-2014-4449 json
iCloud Data Access in Apple iOS before 8.1 does not verify X.509 certificates from TLS servers, which allows man-in-the-middle attackers to…
published 12y ago modified 4mo ago also EUVD-2014-4376
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
iCloud Data Access in Apple iOS before 8.1 does not verify X.509 certificates from TLS servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
Is CVE-2014-4449 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
securityfocus.com
/archive/1/533747
vendor-advisory
-
support.apple.com
/kb/HT6541
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/97665
vdb-entry
-
securitytracker.com
/id/1031077
vdb-entry
-
securityfocus.com
/bid/70659
vdb-entry
-
secunia.com
/advisories/61825
third-party-advisory
Sources
- CVE List CVE-2014-4449
- NVD CVE-2014-4449
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.