{ "CVE_data_meta": { "ASSIGNER": "secalert@redhat.com", "ID": "CVE-2015-8960", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "n/a", "version": { "version_data": [ { "version_value": "n/a" } ] } } ] }, "vendor_name": "n/a" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "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." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "n/a" } ] } ] }, "references": { "reference_data": [ { "name": "[oss-security] 20160920 Re: Possible CVE for TLS protocol issue", "refsource": "MLIST", "url": "http://www.openwall.com/lists/oss-security/2016/09/20/4" }, { "name": "http://twitter.com/matthew_d_green/statuses/630908726950674433", "refsource": "MISC", "url": "http://twitter.com/matthew_d_green/statuses/630908726950674433" }, { "name": "93071", "refsource": "BID", "url": "http://www.securityfocus.com/bid/93071" }, { "name": "https://security.netapp.com/advisory/ntap-20180626-0002/", "refsource": "CONFIRM", "url": "https://security.netapp.com/advisory/ntap-20180626-0002/" }, { "name": "https://www.usenix.org/system/files/conference/woot15/woot15-paper-hlauschek.pdf", "refsource": "MISC", "url": "https://www.usenix.org/system/files/conference/woot15/woot15-paper-hlauschek.pdf" }, { "name": "https://kcitls.org", "refsource": "MISC", "url": "https://kcitls.org" } ] } }