Deprecated SSL and TLS Protocols Supported

The 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.

SeverityMedium
CVSS 3.15.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N Open in the calculator
CVSS 4.06 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-327: Use of a Broken or Risky Cryptographic Algorithm
OWASP Top 10A04:2025 Cryptographic Failures
MITRE ATT&CKT1557 Adversary-in-the-Middle, T1040 Network Sniffing, T1539 Steal Web Session Cookie
CategoryCryptographic Failures

Description

The service accepts connections using one or more deprecated protocol versions: SSL 2.0, SSL 3.0, TLS 1.0 or TLS 1.1. The IETF prohibited SSL 2.0 and SSL 3.0 years ago (RFC 6176 and RFC 7568) and formally deprecated TLS 1.0 and TLS 1.1 in 2021 (RFC 8996), and PCI DSS no longer accepts SSL or early TLS as strong cryptography.

The older versions have design weaknesses that later versions fixed. An attacker able to intercept traffic between a client and the service, for example on shared Wi-Fi or a compromised network segment, may be able to recover secrets such as session cookies from connections that use a deprecated version, and then use them to take over the user's session. SSL 3.0 is open to the POODLE padding oracle attack, and SSL 3.0 and TLS 1.0 to the BEAST attack on CBC-mode encryption; both attacks also need the victim's browser to run script that makes many repeated requests, which an attacker in that position can usually arrange.

TLS 1.0 and TLS 1.1 also rely on MD5 and SHA-1 in their handshake and key derivation, and cannot use the authenticated encryption (AEAD) cipher suites that are now recommended. All mainstream browsers have removed support for these versions, so the realistic exposure is to older clients, embedded devices and scripts that still negotiate them. The risk is higher where SSL 2.0 is enabled, because it is open to DROWN, which needs no action by the victim and can also be used to decrypt modern TLS sessions on any server that shares the same RSA key.

Deprecated versions usually remain enabled because platform defaults were never changed, for compatibility with legacy clients, or on appliances and non-web services (mail, LDAPS, RDP, databases) that are configured separately from the main web servers. The versions a service accepts can be listed with testssl.sh, sslscan, SSLyze or Nmap's ssl-enum-ciphers script, and vulnerability scanners usually report each deprecated version as a separate finding.

Remediation

Disable SSL 2.0, SSL 3.0, TLS 1.0 and TLS 1.1 on every TLS service, leaving only TLS 1.2 and TLS 1.3:

# nginx ssl_protocols TLSv1.2 TLSv1.3; # Apache httpd (mod_ssl); omit +TLSv1.3 where the build does not support it SSLProtocol -all +TLSv1.2 +TLSv1.3
  • On Windows (IIS, RDP, AD FS, Exchange and other services that use Schannel), create the key HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server with the DWORD values Enabled set to 0 and DisabledByDefault set to 1, repeat this for SSL 2.0, SSL 3.0 and TLS 1.1, and do the same under each version's Client key for outbound connections, then restart the server.
  • For Java services, list the old versions in the jdk.tls.disabledAlgorithms security property. For load balancers, CDNs and appliances, select a TLS policy or profile that allows only TLS 1.2 and later.
  • Include mail, directory, database, VPN and management interfaces, which are often configured separately.

Before disabling a version, check server or load balancer logs for clients that still use it and arrange for them to be updated. Where an old version must remain for a short time, restrict it to the systems that need it and confirm that the server supports TLS_FALLBACK_SCSV (RFC 7507), which lets it refuse a downgraded connection from a client that supports a newer version. Confirm the fix by rescanning each service and checking that only TLS 1.2 and TLS 1.3 are accepted.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More TLS and Certificates Findings

Every TLS and Certificates finding