Weak TLS Cipher Suites Supported
The 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.
| Severity | Medium |
| CVSS 3.1 | 5.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.0 | 6 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 |
| CWE | CWE-327: Use of a Broken or Risky Cryptographic Algorithm |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| MITRE ATT&CK | T1040 Network Sniffing, T1557 Adversary-in-the-Middle, T1539 Steal Web Session Cookie |
| Category | Cryptographic Failures |
Description
The service accepts one or more cipher suites whose encryption is no longer considered adequate. An attacker who can observe or intercept traffic could recover secrets sent repeatedly over connections that use a weak suite, such as session cookies, authorisation headers or passwords, and use them to access the user's account. The variants met most often are:
- RC4, a stream cipher with statistical biases that allow plaintext sent repeatedly to be recovered from enough encrypted copies. RFC 7465 prohibits RC4 in TLS.
- Triple DES (3DES) and other 64-bit block ciphers such as IDEA, which are open to birthday attacks once a large volume of data has been encrypted under one key in a long-lived connection (Sweet32, CVE-2016-2183). The RC4 and Sweet32 attacks need a very large number of encryptions of the same secret, usually generated by script running in the victim's browser over many hours, so they are slow and conspicuous, but they rely on nothing beyond the cipher itself.
- Single DES and export-grade suites with 56-bit or 40-bit keys, which are far weaker: they can be broken outright with modest resources and were abused in the FREAK and Logjam downgrade attacks, so where a client can be made to use one, an attacker can decrypt or alter the session.
- Suites using MD5 for message authentication, which are not known to be broken in TLS but fall well short of current recommendations.
Weak suites usually remain because the cipher list was set years ago, is built from broad keywords, or keeps old suites for legacy clients. Whether one is actually used depends on what the client offers and whose preference order the server follows, so a server that enforces its own order and lists a weak suite early can select it even when a stronger one is available. Current browsers no longer offer RC4, DES or export suites, which limits the exposure to older clients and non-browser software.
The accepted suites can be listed with testssl.sh, sslscan, SSLyze or Nmap's ssl-enum-ciphers script. Vulnerability scanners usually report RC4 and 3DES as separate findings, the latter often under the name Sweet32.
Remediation
Remove every weak suite from the service's configuration and offer only suites with forward secrecy and authenticated encryption (AES-GCM or ChaCha20-Poly1305), using an explicit list rather than broad keywords such as ALL, whose contents depend on the library version:
- On Windows, set the content and order of the list through Group Policy (
Computer Configuration > Administrative Templates > Network > SSL Configuration Settings > SSL Cipher Suite Order) or remove individual suites with theDisable-TlsCipherSuitePowerShell cmdlet, then restart the server. - For Java, make sure
RC4,DESand3DES_EDE_CBCremain in thejdk.tls.disabledAlgorithmssecurity property, as they are in current releases, and that no application setting re-enables them. - For load balancers, CDNs and appliances, select a TLS policy or cipher profile that excludes them.
Where a legacy client still needs an older suite, place strong suites first in the server's order and plan the client's upgrade. Confirm the fix by listing the accepted suites again and checking that no RC4, DES, 3DES, IDEA, export or MD5-based suite remains.
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.