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

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

Informational3


The Other Areas

Every One of These, in Your Own Library.

In Pental the finding library is in Settings, Library: add the findings you write most, rated in your firm's CVSS version, and make them your own. Free trial, no card required.