The TLS protocol 1.2 and earlier supports the rsa_fixed_dh, dss_fixed_dh, rsa_fixed_ecdh, and ecdsa_fixed_ecdh values for ClientCertificateType but does not directly document the ability to compute the master secret in certain situations with a client secret key and server public key but not a server secret key, which makes it easier for man-in-the-middle attackers to spoof TLS servers by leveraging knowledge of the secret key for an arbitrary installed client X.509 certificate, aka the "Key Compromise Impersonation (KCI)" issue.
References
| Link | Resource |
|---|---|
| https://www.usenix.org/system/files/conference/woot15/woot15-paper-hlauschek.pdf | Technical Description |
| http://twitter.com/matthew_d_green/statuses/630908726950674433 | Press/Media Coverage |
| http://www.openwall.com/lists/oss-security/2016/09/20/4 | Mailing List Third Party Advisory |
| https://kcitls.org | Technical Description |
| http://www.securityfocus.com/bid/93071 | |
| https://security.netapp.com/advisory/ntap-20180626-0002/ |
Configurations
Configuration 1 (hide)
|
Information
Published : 2016-09-21 02:59
Updated : 2018-06-28 01:29
NVD link : CVE-2015-8960
Mitre link : CVE-2015-8960
JSON object : View
Products Affected
microsoft
- internet_explorer
opera
- opera
mozilla
- firefox
- chrome
apple
- safari
CWE
CWE-310
Cryptographic Issues
