TLS/SSL Misconfiguration
detect, understand, remediate
TLS/SSL misconfigurations (deprecated protocols, weak ciphers, expired certificates, and missing HSTS) expose encrypted communications to interception and downgrade attacks.
No credit card required. Free plan available forever.
What is a TLS/SSL misconfiguration?
TLS/SSL misconfigurations occur when a server's transport encryption is improperly configured: supporting deprecated protocols (TLS 1.0, TLS 1.1, SSLv3), using weak cipher suites, presenting expired or misconfigured certificates, or lacking HTTP Strict Transport Security (HSTS). These weaknesses allow attackers to intercept, decrypt, or tamper with data in transit.
Even when encryption is present, a misconfigured TLS implementation can be as dangerous as no encryption at all. Deprecated protocols have known vulnerabilities (POODLE, BEAST, CRIME) that enable active attackers to decrypt traffic. Weak cipher suites can be brute-forced, and expired certificates cause browsers to display warnings that train users to click through security prompts.
TLS misconfigurations are especially critical for applications handling sensitive data, including financial transactions, healthcare records, authentication credentials, and personal information. Regulatory frameworks like PCI DSS explicitly require strong encryption standards, making TLS misconfiguration both a security risk and a compliance violation.
How it works
Scan TLS configuration
Attacker uses tools like sslyze, testssl.sh, or nmap to enumerate supported protocols, cipher suites, and certificate details on the target server.
Identify weakness
Deprecated protocols (TLS 1.0/1.1), weak ciphers (RC4, DES, export ciphers), missing HSTS, or certificate issues (expired, self-signed, wrong hostname) are identified.
Perform downgrade attack
In a man-in-the-middle position, the attacker forces the client and server to negotiate a weak protocol or cipher suite that can be exploited.
Decrypt or modify traffic
Using the negotiated weak encryption, the attacker decrypts sensitive data in transit, including credentials, session tokens, personal data, and financial information.
Common causes
Legacy protocol support
Keeping TLS 1.0 and TLS 1.1 enabled for backward compatibility with older clients, despite these protocols having known cryptographic weaknesses.
Default cipher suite configuration
Using the server or framework's default cipher suite list without auditing it. Many defaults include weak or export-grade ciphers for compatibility.
Unmonitored certificate expiry
Failing to track certificate expiration dates, leading to expired certificates that cause browser warnings and erode user trust in security prompts.
Missing HSTS and preload
Not deploying HTTP Strict Transport Security headers, which means the first request to the site can be intercepted before the redirect to HTTPS occurs.
How to detect it
Automated detection
- SecPortal's SSL/TLS scanner checks for deprecated protocols, weak ciphers, certificate validity, and HSTS configuration across all your domains
- Continuous monitoring alerts you when certificates approach expiration or when new TLS vulnerabilities affect your cipher suite configuration
- Security header analysis flags missing HSTS headers, incorrect max-age values, and missing includeSubDomains or preload directives
Manual testing
- Use openssl s_client to connect with specific protocol versions and cipher suites to confirm what the server accepts
- Check certificate chain completeness, as missing intermediate certificates cause validation failures on some clients
- Verify HSTS header presence, max-age value (should be at least 31536000), and includeSubDomains directive in browser developer tools
How to fix it
Enforce TLS 1.2 and TLS 1.3 only
Disable SSLv3, TLS 1.0, and TLS 1.1 on all servers. TLS 1.2 with strong cipher suites is the minimum; TLS 1.3 is preferred for its improved security and performance.
Configure strong cipher suites
Use only AEAD cipher suites (AES-GCM, ChaCha20-Poly1305). Disable CBC mode ciphers, RC4, DES, 3DES, and all export-grade ciphers. Prefer forward secrecy (ECDHE).
Automate certificate renewal
Use automated certificate management (e.g. Let's Encrypt with certbot) to ensure certificates are renewed well before expiration. Monitor certificate expiry dates with alerting.
Deploy HSTS with preload
Set the Strict-Transport-Security header with max-age=31536000, includeSubDomains, and preload. Submit your domain to the HSTS preload list for maximum protection.
Disable CBC mode ciphers
CBC cipher suites are vulnerable to padding oracle attacks (POODLE, Lucky13). Remove all CBC ciphers and use only GCM or ChaCha20-Poly1305 authenticated encryption.
Compliance impact
Check your SSL/TLS configuration
SecPortal checks certificates, protocols, ciphers, and HSTS in every external scan. Start free.
No credit card required. Free plan available forever.