Common TLS Attacks and Mitigations
You'll learn: How real-world attacks like BEAST, CRIME, and Heartbleed exploited TLS weaknesses, and how modern TLS versions protect against them.
Why TLS Gets Attacked
Even though TLS encrypts traffic, attackers have discovered clever ways to exploit implementation flaws, protocol weaknesses, and side channels. Understanding these attacks helps explain why we constantly update TLS versions and cipher suites.
Major Historical Attacks
BEAST (Browser Exploit Against SSL/TLS)
This 2011 attack exploited a weakness in TLS 1.0's CBC (cipher block chaining) mode. Attackers could predict initialization vectors and decrypt HTTPS cookies by observing patterns in encrypted traffic.
Mitigation: TLS 1.1+ randomizes initialization vectors properly. Modern browsers also use client-side workarounds.
CRIME (Compression Ratio Info-leak Made Easy)
CRIME exploited TLS compression to reveal session cookies. By injecting known data and measuring compressed size changes, attackers could guess secret values byte-by-byte (like a "hot/cold" game).
Mitigation: TLS compression is now disabled by default in all modern implementations.
Heartbleed
This 2014 bug in OpenSSL's heartbeat extension allowed attackers to read server memory, potentially exposing private keys, passwords, and session data. It wasn't a protocol flaw—just catastrophic implementation negligence in bounds checking.
Mitigation: Immediate patching, key rotation, and more rigorous code review practices.
Modern Protections
TLS 1.3 eliminates many attack surfaces by:
- Removing vulnerable cipher modes (CBC, RC4)
- Requiring Perfect Forward Secrecy
- Simplifying the handshake to reduce attack windows
- Encrypting more of the handshake itself
Key Takeaway: Historic TLS attacks like BEAST, CRIME, and Heartbleed exploited specific implementation flaws and protocol weaknesses; modern TLS versions prevent them through simplified designs, stronger defaults, and removal of vulnerable features.