TLS and Certificates Findings.
20 findings in TLS and certificates, each written up as a report carries it: what the weakness is and what it lets an attacker do, the fix, CVSS 3.1 and 4.0 ratings, the CWE and the references.
High3
OpenSSL Heartbleed (CVE-2014-0160)CVSS 7.5 · CWE-130The service uses an OpenSSL version vulnerable to Heartbleed, which lets anyone read chunks of the server's memory, including private keys, passwords and session data.NULL or Anonymous TLS Cipher Suites SupportedCVSS 7.4 · CWE-327The service accepts NULL cipher suites, which send data unencrypted, or anonymous suites, which encrypt without authenticating the server, removing the protection TLS should give.OpenSSL ChangeCipherSpec Injection (CVE-2014-0224)CVSS 7.4 · CWE-841The service uses an OpenSSL version that accepts ChangeCipherSpec messages too early, letting an attacker in the middle force weak keys and read or alter traffic with vulnerable clients.
Medium10
Expired TLS CertificateCVSS 6.8 · CWE-324The service presents a TLS certificate whose validity period has ended, so clients reject it or warn their users, who may then learn to ignore certificate warnings.TLS Certificate Hostname MismatchCVSS 6.8 · CWE-297The service presents a TLS certificate that is not valid for the name clients use to reach it, so clients warn or refuse, and users may learn to ignore certificate warnings.Untrusted TLS CertificateCVSS 6.8 · CWE-295The service presents a certificate that clients cannot trust, such as a self-signed certificate or one from a private authority, so they cannot confirm they reached the genuine server.RSA Key Exchange Padding Oracle (ROBOT)CVSS 5.9 · CWE-203The service's handling of RSA key exchange reveals whether decrypted data was correctly padded, giving attackers an oracle to decrypt recorded sessions or sign as the server.Deprecated SSL and TLS Protocols SupportedCVSS 5.3 · CWE-327The service accepts SSL 2.0, SSL 3.0, TLS 1.0 or TLS 1.1, protocol versions with known cryptographic weaknesses that current standards and browsers no longer permit.Weak TLS Cipher Suites SupportedCVSS 5.3 · CWE-327The service accepts cipher suites with weak encryption, such as RC4, Triple DES, single DES or export-grade suites, which can let an attacker recover parts of encrypted traffic.Insecure TLS Renegotiation SupportedCVSS 4.8 · CWE-300The service allows TLS renegotiation without the RFC 5746 secure renegotiation extension, letting an attacker in the middle inject data at the start of a victim's session.Revoked TLS CertificateCVSS 4.8 · CWE-299The service presents a TLS certificate that its issuing authority has revoked, which clients checking revocation refuse, and which may mean its private key was compromised.TLS Certificate Signed Using a Weak Hashing AlgorithmCVSS 4.8 · CWE-328The service's certificate, or one in its chain, is signed using MD5 or SHA-1, hash algorithms broken by collision attacks, which many current clients reject.TLS Certificate With an Insufficient Key LengthCVSS 4.8 · CWE-326The service's certificate uses a public key that is too short, such as an RSA key under 2048 bits, which a well-resourced attacker could break to impersonate the service.
Low4
TLS Forward Secrecy Not SupportedCVSS 3.7 · CWE-326The service negotiates key exchanges without forward secrecy, such as static RSA, so anyone who later obtains its private key could decrypt previously recorded sessions.Weak Diffie-Hellman Key Exchange ParametersCVSS 3.7 · CWE-326The service uses Diffie-Hellman key exchange with a group of 1024 bits or fewer, which a well-resourced attacker could break to decrypt the sessions that rely on it.Incomplete TLS Certificate ChainCVSS 3.1 · CWE-296The service does not send the intermediate certificates that link its certificate to a trusted root, so some clients cannot validate it and fail or show a warning.TLS Compression Enabled (CRIME)CVSS 3.1 · CWE-203The service supports TLS-level compression, which lets an attacker who can observe traffic and influence requests recover secrets such as session cookies (the CRIME attack).
Informational3
TLS 1.3 Not SupportedCVSS 0 · CWE-326The service does not support TLS 1.3, the current version of the protocol, so its connections cannot benefit from the newer version's stronger handshake and safer cipher suites.TLS Certificate Expiring SoonCVSS 0 · CWE-324The service's TLS certificate is still valid but expires soon, and unless it is renewed in time clients will start to reject it or warn their users.Wildcard TLS Certificate in UseCVSS 0 · CWE-653The service uses a wildcard certificate, valid for every host name at one level of a domain, so the compromise of any system holding its key affects all of them.
The Other Areas
Web Applications 87Authentication and Sessions 32APIs 16Network Services 56Internal Networks 9Active Directory 44Windows and Linux Hosts 29Patching and Outdated Software 36AWS 19Azure and Microsoft 365 19Google Cloud 11Containers and Kubernetes 17Mobile Applications 22Wireless 11Email and DNS 11Thick Clients 11Source Code and Supply Chain 13AI and LLM Applications 8Social Engineering and Physical 14IoT and OT 5