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
Configurations
Configuration 1 (hide)
AND |
|
Configuration 2 (hide)
|
History
No history.
Information
Published : 2016-09-21 02:59
Updated : 2025-04-12 10:46
NVD link : CVE-2015-8960
Mitre link : CVE-2015-8960
CVE.ORG link : CVE-2015-8960
JSON object : View
Products Affected
netapp
- data_ontap_edge
- snapmanager
- snap_creator_framework
- solidfire_\&_hci_management_node
- system_setup
- plug-in_for_symantec_netbackup
- snapprotect
- smi-s_provider
- clustered_data_ontap_antivirus_connector
- oncommand_shift
- host_agent
- snapdrive
ietf
- transport_layer_security
- chrome
opera
- opera_browser
apple
- safari
mozilla
- firefox
microsoft
- internet_explorer
CWE
CWE-295
Improper Certificate Validation