BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.bsidescbr.com.au//bsides-canberra-2026//speaker//Z7Q
 JTJ
BEGIN:VTIMEZONE
TZID:AEST
BEGIN:STANDARD
DTSTART:20000326T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3;UNTIL=20050326T170000Z
TZNAME:AEST
TZOFFSETFROM:+1100
TZOFFSETTO:+1000
END:STANDARD
BEGIN:STANDARD
DTSTART:20060402T040000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060401T170000Z
TZNAME:AEST
TZOFFSETFROM:+1100
TZOFFSETTO:+1000
END:STANDARD
BEGIN:STANDARD
DTSTART:20070325T040000
RRULE:FREQ=YEARLY;BYDAY=4SU;BYMONTH=3;UNTIL=20070324T170000Z
TZNAME:AEST
TZOFFSETFROM:+1100
TZOFFSETTO:+1000
END:STANDARD
BEGIN:STANDARD
DTSTART:20080406T040000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
TZNAME:AEST
TZOFFSETFROM:+1100
TZOFFSETTO:+1000
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000827T030000
RRULE:FREQ=YEARLY;BYDAY=4SU;BYMONTH=8;UNTIL=20000826T170000Z
TZNAME:AEDT
TZOFFSETFROM:+1000
TZOFFSETTO:+1100
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20011028T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20071027T170000Z
TZNAME:AEDT
TZOFFSETFROM:+1000
TZOFFSETTO:+1100
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20081005T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=10
TZNAME:AEDT
TZOFFSETFROM:+1000
TZOFFSETTO:+1100
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-bsides-canberra-2026-ZREJ37@cfp.bsidescbr.com.au
DTSTART;TZID=AEST:20260925T151500
DTEND;TZID=AEST:20260925T161000
DESCRIPTION:Cryptographic padding oracle vulnerabilities are far from new. 
 If you can throw crafted ciphertext at a Cipher Block Chaining (CBC) decry
 ption endpoint\, and it is kind enough to tell you whether it was a paddin
 g error or something else that caused it to blow up\, you can use some cra
 fty block algebra to turn it into a byte-by-byte decryption/encryption mac
 hine.\n\nIt may be tempting to fix a padding oracle vulnerability by norma
 lising the error messages. Instead of saying\, "Oops\, there was a padding
  error!" simply say "Oops\, there was an error." Better yet\, just return 
 a generic HTTP 500 response.\n\nThe problem is that error messages are onl
 y a symptom of padding oracles\, they are not the root cause. Any kind of 
 divergent code path behaviour can give rise to a subtle sub-millisecond ti
 ming difference\, which can be just enough to reveal the secrets of a padd
 ing oracle.\n\nJustin will walk you through the methodology behind CBC pad
 ding oracle exploitation\, the curse of WAN jitter that can destroy a frag
 ile timing signal\, and the blessing of Timeless Timing Attacks (Van Goeth
 em et al.\, 2020) which uses HTTP/2 co-scheduling to sniff out even the fa
 intest of timing differentials.\n\nJoin us to hear about the full suite of
  Timeless Timing Attacks tooling we're releasing at BSides Canberra 2026 i
 ncluding Go libraries\, statistical engines\, and command-line tools. Lear
 n how to exploit time-based padding oracle vulnerabilities\, get bamboozle
 d by statistical methodologies you thought you'd never have to hear about 
 again\, and wonder whether there are other "obvious" vulnerability fixes t
 hat could come undone given careful consideration of time. We can't wait t
 o hear what you come up with!
DTSTAMP:20260715T203850Z
LOCATION:Main Track
SUMMARY:Time Crisis: Exploiting time-based padding oracle vulnerabilities u
 sing Timeless Timing Attacks - Justin Steven
URL:https://cfp.bsidescbr.com.au/bsides-canberra-2026/talk/ZREJ37/
END:VEVENT
END:VCALENDAR