Skip to content
Fencer Intel
high 7.4

CVE-2014-1266 json

The SSLVerifySignedServerKeyExchange function in libsecurity_ssl/lib/sslKeyExchange.c in the Secure Transport feature in the Data Security…

published 12y ago modified 4mo ago also EUVD-2014-1344

cvss
7.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.7%
EPSS 5.7% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

The SSLVerifySignedServerKeyExchange function in libsecurity_ssl/lib/sslKeyExchange.c in the Secure Transport feature in the Data Security component in Apple iOS 6.x before 6.1.6 and 7.x before 7.0.6, Apple TV 6.x before 6.0.2, and Apple OS X 10.9.x before 10.9.2 does not check the signature in a TLS Server Key Exchange message, which allows man-in-the-middle attackers to spoof SSL servers by (1) using an arbitrary private key for the signing step or (2) omitting the signing step.

Patch / fix

  • apple iphone_os 6.1.6, 7.0.6
  • apple mac_os_x 10.9.2
  • apple tvos 6.0.2

Is CVE-2014-1266 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 Fencer

Exploit prediction

5.74% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • cs.columbia.edu https://www.cs.columbia.edu/~smb/blog/2014-02/2014-02-23.html referenced PoC, tagged "exploit" by a source, unverified
  • cs.columbia.edu https://www.cs.columbia.edu/~smb/blog/2014-02/2014-02-24.html referenced PoC, tagged "exploit" by a source, unverified
  • imperialviolet.org https://www.imperialviolet.org/2014/02/22/applebug.html referenced PoC, tagged "exploit" by a source, unverified
  • news.ycombinator.com https://news.ycombinator.com/item?id=7281378 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

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.