Case DA730F · Cryptography · L4 Advanced

What Broken TLS Taught Us

Practise as: Deep diveLevel: L4 Advanced
  1. 01 Context
  2. 02 Mechanism
  3. 03 Lessons
What a strong answer covers

Try it out loud first. Then check yourself:

  1. CBC in old TLS: BEAST used predictable IVs in TLS 1.0; Lucky13 used MAC-then-encrypt timing; POODLE broke SSLv3 padding.
  2. Downgrades: FREAK and Logjam tricked peers into export-grade RSA or DH that could be broken in practice.
  3. RSA PKCS#1 v1.5 key exchange: Bleichenbacher oracles kept returning (ROBOT, 2017), enabling decryption or signing.
  4. Compression (CRIME, BREACH) leaked secrets through ciphertext length when attacker-controlled data shared a compressed stream.
  5. TLS 1.3 response: removed CBC, RSA key exchange, compression and custom DH groups; signs the transcript; adds downgrade sentinels.

If the interviewer pushes back

  • BREACH targets HTTP-level compression, which TLS 1.3 does not control. How do applications mitigate it?
  • Why is removing options safer than making each option secure, and where has TLS 1.3 still left foot-guns (e.g. 0-RTT)?

Go deeper

More Cryptography cards

All Cryptography cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09