TLS 1.3 Not Supported
The 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.
| Severity | Informational |
| CVSS 3.1 | 0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N Open in the calculator |
| CVSS 4.0 | 0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-326: Inadequate Encryption Strength |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| Category | Cryptographic Failures |
Description
The service supports TLS 1.2 but not TLS 1.3. TLS 1.2 remains acceptable when configured with strong cipher suites, so this is not a vulnerability in itself and has no direct impact, but TLS 1.3 (RFC 8446) removes whole classes of weakness by design and is now the recommended default.
TLS 1.3 drops RSA key exchange, static Diffie-Hellman, CBC-mode and RC4 encryption, compression and renegotiation, leaving only authenticated encryption suites with forward secrecy, so many of the configuration errors reported against TLS 1.2 services cannot occur. It also encrypts more of the handshake, including the server's certificate, protects the negotiation against downgrade, and needs one fewer round trip to establish a connection. Without it, the service relies entirely on its TLS 1.2 configuration being correct, and clients lose the extra protection of the encrypted handshake and built-in downgrade protection.
Support depends on the TLS library and server software: OpenSSL added TLS 1.3 in its 1.1.1 release, Java in Java 11, and Windows Schannel in Windows Server 2022 and Windows 11, so services on older platforms cannot offer it without an upgrade. A missing TLS 1.3 therefore often indicates an older TLS library or operating system, which may carry other unpatched weaknesses. Its absence is shown by testssl.sh, sslscan and SSLyze, and vulnerability scanners usually report it as informational.
Remediation
Enable TLS 1.3 alongside TLS 1.2, upgrading the TLS library, server software or operating system where it does not support the newer version:
- On Windows Server 2022 and later, TLS 1.3 is enabled by default in Schannel; check that it has not been disabled under
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3. - For load balancers, CDNs and cloud services, select a TLS policy that includes TLS 1.3.
- Leave 0-RTT (early data) disabled, for example
ssl_early_data offin nginx, unless the application has been reviewed for replay, because data sent as early data can be replayed by an attacker. - Test interception proxies, firewalls and monitoring tools on the network path, as some older middleboxes handle TLS 1.3 poorly.
Confirm the change by connecting with a TLS 1.3 client, for example openssl s_client with the -tls1_3 option, or by rescanning the service.
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 trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.