How to fix: Weak TLS Protocol Version
Async check: reports whether the negotiated TLS protocol is TLS 1.2+ or older (TLS 1.0/1.1/SSLv3).
Why it matters
Older TLS versions have known attacks (POODLE, BEAST, ROBOT) and lack modern AEAD cipher suites. Clients negotiating TLS 1.0 or 1.1 are vulnerable to downgrade attacks.
TLS 1.0 and 1.1 have been deprecated by IETF (RFC 8996). Most browsers and APIs no longer support them.
How to fix it
- 1Disable TLS 1.0 and 1.1 on the server.
- 2Keep TLS 1.2 and 1.3 enabled.
- 3Prefer AEAD ciphers (AES-GCM, ChaCha20-Poly1305).
Code examples
Nginx
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305;
ssl_prefer_server_ciphers off;References
Detected automatically by VulnRadar. The check id is tls-protocol-version, stable across every scan so you can filter or diff on it.
More tls checks
Questions
- How severe is Weak TLS Protocol Version?
- VulnRadar rates this high severity in the tls category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id tls-protocol-version, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Weak TLS Protocol Version map to?
- It maps to CWE-326. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.