Case DA730F · Cryptography · L4 Advanced
What Broken TLS Taught Us
- 01 Context
- 02 Mechanism
- 03 Lessons
What a strong answer covers
Try it out loud first. Then check yourself:
- CBC in old TLS: BEAST used predictable IVs in TLS 1.0; Lucky13 used MAC-then-encrypt timing; POODLE broke SSLv3 padding.
- Downgrades: FREAK and Logjam tricked peers into export-grade RSA or DH that could be broken in practice.
- RSA PKCS#1 v1.5 key exchange: Bleichenbacher oracles kept returning (ROBOT, 2017), enabling decryption or signing.
- Compression (CRIME, BREACH) leaked secrets through ciphertext length when attacker-controlled data shared a compressed stream.
- 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)?