SSL/TLS Exhaustion Attack
An SSL/TLS Exhaustion Attack is a form of Distributed Denial-of-Service (DDoS) attack that targets the computational cost of establishing Secure Sockets Layer (SSL) or Transport Layer Security (TLS) connections. Rather than exploiting software vulnerabilities, this attack abuses the resource-intensive nature of the SSL/TLS handshake process to exhaust server-side resources, rendering services unresponsive.
How It Works
When a client initiates a secure connection to a server using HTTPS (which relies on SSL/TLS), the handshake process includes several steps:
-
Key exchange
-
Authentication
-
Cipher agreement
-
Session setup
This process is computationally expensive, particularly when using public-key cryptography (e.g., RSA or ECC). Each new connection requires the server to perform CPU-intensive operations.
In an SSL Exhaustion Attack, the attacker floods the target server with a large number of SSL handshake requests—often with incomplete, slow, or malformed connections. The server attempts to process each handshake, which consumes CPU, memory, and thread pool resources. Legitimate user connections are then delayed or dropped due to resource depletion.
Attackers may use tools or botnets to scale the attack, making it harder to distinguish legitimate clients from malicious ones.
Types of SSL Exhaustion Techniques
-
Full SSL Handshake Flood:
-
Each bot completes full handshakes with high frequency, exhausting CPU and thread pools.
-
-
Partial or Slow Handshakes:
-
Attackers initiate handshakes but delay or never complete them, tying up server resources longer.
-
-
SSL Renegotiation Abuse:
-
Repeatedly requesting renegotiation within an existing connection, forcing new key computations.
-
-
Certificate Flooding:
-
Repeated handshake attempts requesting complex or uncommon cipher suites to maximize server workload.
-
Impact
-
Service Unavailability: Target server may become unable to handle legitimate requests.
-
Resource Starvation: High CPU usage, thread pool exhaustion, and memory consumption.
-
Security Device Degradation: Devices like SSL offloaders, WAFs, or load balancers can also be overwhelmed.
-
Reputation Damage: Affected services can suffer from downtime and loss of user trust.
Detection and Mitigation
-
Rate Limiting: Restrict the number of new SSL/TLS handshakes per IP over time.
-
Connection Timeouts: Set aggressive timeouts for incomplete or slow handshakes.
-
SSL Offloading: Use dedicated hardware (e.g., Application Delivery Controllers) to offload SSL processing.
-
Behavioral Analysis: Monitor for anomalous handshake patterns or cipher suite requests.
-
CAPTCHA & Bot Detection: Enforce human validation at the application layer before SSL initiation.
Adoption of TLS 1.3: Transitioning to TLS 1.3, which has a more efficient handshake process, can mitigate some attack vectors.
Common Targets
-
HTTPS web servers
-
Load balancers and reverse proxies
-
SSL offloading appliances
-
API gateways and authentication servers
by Sergei Penchuk, CISSP