Transport Layer Security
Approved changes feed: RSS · Atom
cpe:2.3:a:ietf:transport_layer_security:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Ietf (04b4646c-6b5e-5c7e-9409-3fa11d21c1be) |
|---|---|
| Product | Transport Layer Security (cee55040-385a-5361-969d-51aa99a344fa) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2015-8960 |
vulnerable | 2026-06-03 14:35:13.734807 |
Details available
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.
Published: 2016-09-21T01:00:00.000Z
Updated: 2024-08-06T08:36:30.681Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.