01Description
Services were found to support cipher suites considered weak, such as those using 3DES, RC4, CBC mode with SHA-1, or key exchange without forward secrecy.
02Impact
Weak cipher suites reduce the confidentiality of data in transit and, in some cases, are vulnerable to known attacks such as SWEET32 against 64-bit block ciphers. Ciphers without forward secrecy mean that a future compromise of the server key would expose previously recorded traffic.
03Severity
Typically
Low
Typically Low. Usually Low. Raise to Medium if export-grade, NULL or anonymous ciphers are offered, as these can allow decryption or impersonation.
04How to verify
- 1Enumerate supported cipher suites with testssl.sh, sslscan or nmap's ssl-enum-ciphers script.
- 2Record weak suites per host and port.
- 3Note whether the server enforces its own cipher preference order.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Restrict cipher suites to modern AEAD ciphers (AES-GCM and ChaCha20-Poly1305) with ECDHE key exchange.
- 2Remove 3DES, RC4, NULL, EXPORT and anonymous suites entirely.
- 3Use a maintained baseline such as the Mozilla 'intermediate' TLS configuration.
- 4Re-scan after the change.
Draft findings like this from your own evidence
Book a demo