4 ms·
This is pretty big. Heartbleed was exactly this but with the heartbeat extension instead of the session ticket extension, and with OpenSSL instead of F5's TLS i
by baby 10y ago
This is pretty big. Heartbleed was exactly this but with the heartbeat extension instead of the session ticket extension, and with OpenSSL instead of F5's TLS implementation.
- huhtenberg 10y ago> ... a vulnerability ... of certain F5 products I.e. this being "big" depends on whether you have "certain F5 products" in your setup.
- baby 10y agosame with OpenSSL really.
- strictnein 10y agoThere's a pretty big difference in the amount of memory leaked. Ticketbleed reveals 31 Bytes of uninitialized memory. Heartbleed revealed 64KB.
- baby 10y agoIn the end it doesn't mean that Ticketbleed would reveal a private key more slowly. But since nobody proved that this vuln is exploitable... Heartbleed was proven exploitable thanks to Cloudflare who organized a challenge. (It was also easier to test for exploitability.)
- kayfox 10y agoSession tickets are not enabled by default on F5 Big-IP.