BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//event.sec-t.org//sec-t-2025//speaker//HMBXFF
BEGIN:VTIMEZONE
TZID:Europe/Stockholm
BEGIN:DAYLIGHT
DTSTART:20240911T000000
TZNAME:CEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20241027T030000
RDATE:20251026T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20250330T030000
RDATE:20260329T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Unicode as low-level attack primitive - noraj
DTSTART;TZID=Europe/Stockholm:20250911T094500
DTEND;TZID=Europe/Stockholm:20250911T101500
DTSTAMP:20261115T023031Z
UID:pretalx-sec-t-2025-DS3EAC@event.sec-t.org
DESCRIPTION:Whether it is for applications\, operating systems\, databases
 \, etc. anything that reads\, writes\, manipulates data must be using an e
 ncoding. On modern days\, it will mostly always be UTF-8 by default\, some
 times UTF-16\, both are Unicode standards. Security auditors and researche
 rs often manipulate data or protocols\, but what about manipulating the un
 derlying encoding?\n\nUnicode has become the one encoding to rule them all
 \, replacing hundreds of old standards. At first glance\, it could feel li
 ke a simplification. It is not. All those old encodings where ultra-basic 
 while Unicode is overwhelmingly complex beyond what you can imagine until 
 reading the specifications.\n\nOver the years\, the lack of awareness abou
 t Unicode and its complexity have led to a lot of issues and implementatio
 n errors. The version 16.0 of the Unicode Standard is 1140 pages long\, an
 d there are over 60 UAX (Unicode Standard Annexes)\, UTS (Unicode Technica
 l Standards)\, UTR (Unicode Technical Reports)\, each of which is comparab
 le to an IETF RFC. During the last 3 years\, I have analysed about 15 prog
 ramming languages\, none of which is fully implementing 100% of the Unicod
 e standard.\n\nAny piece of software around you is probably using Unicode
 \, but none of them have complete implementation of it and all of them a p
 robably different. What could go wrong?
LOCATION:Main hall
URL:https://event.sec-t.org/sec-t-2025/talk/DS3EAC/
END:VEVENT
END:VCALENDAR
