Skip to main content
MediumTLSOWASP A02:2021CWE-327

How to fix: Server still accepts TLS 1.0 or TLS 1.1

A second handshake offering only TLS 1.0 and TLS 1.1 completed successfully against this host. That proves the server still accepts a deprecated version even when it prefers a modern one with a modern client.

Why it matters

TLS 1.0 and 1.1 depend on constructions no longer considered sound: MAC-then-encrypt CBC modes, MD5 and SHA-1 inside the PRF and in signatures, and no AEAD suites. An old client, or one an attacker can influence into downgrading, ends up on a protocol with published attacks against it. PCI DSS has disallowed TLS 1.0 since June 2018.

The evidence here is deliberately one-directional. A successful legacy handshake proves the server accepts the version. A failed one proves nothing, because the scanning client's own TLS library may refuse those suites regardless of what the server would have done, so this check never reports that legacy protocols are disabled, only that they are enabled. It is also distinct from reporting the negotiated version: a server can prefer TLS 1.3 and still answer a 1.0 client.

How to fix it

  1. 1Set the minimum protocol version to TLS 1.2 on every listener, load balancer and CDN in front of the site.
  2. 2Check the edge and the origin separately: their protocol settings are usually configured independently.
  3. 3Review client analytics before disabling, since a small number of very old clients will lose access.
  4. 4Re-test afterwards with an explicit legacy handshake rather than trusting the configuration file.

Code examples

Nginx and Apache: TLS 1.2 minimum

nginx
# nginx
ssl_protocols TLSv1.2 TLSv1.3;

# apache
# SSLProtocol -all +TLSv1.2 +TLSv1.3

Confirm the legacy versions are refused

bash
openssl s_client -connect example.com:443 -tls1 </dev/null
openssl s_client -connect example.com:443 -tls1_1 </dev/null
# both should fail to complete a handshake

References

Detected automatically by VulnRadar. The check id is tls-legacy-protocol-accepted, stable across every scan so you can filter or diff on it.

See every tls check

Questions

How severe is Server still accepts TLS 1.0 or TLS 1.1?
VulnRadar rates this medium 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-legacy-protocol-accepted, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Server still accepts TLS 1.0 or TLS 1.1 map to?
It maps to CWE-327. 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.

Propose a checkHow a check is built

Scan your own site for server still accepts tls 1.0 or tls 1.1

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Server still accepts TLS 1.0 or TLS 1.1 fix | VulnRadar