Steering Clear of Danger: Decrypting the Realities of Remote Car Hacking
summary
Explains how remote car takeovers actually work: fuzzing a GENIVI-based connection manager using a Mayhem docker image reproduces the Pwn2Own exploit that triggers a stack-based buffer overflow via malformed DHCP/DNS compression; weaponization chain includes canary bypass, ASLR leak from an out‑of‑bounds read, mmap/munprotect to execute shellcode and open doors, and the demo works end‑to‑end. Also shows hunting exposed APIs with crt.sh and salvaging open‑source IVI firmware from vendors.
AI-written summary · about
chapters (16)
- 0:00Car hacking basics
- 1:01Talk overview
- 3:06Car exploitation steps
- 6:40Attack surface mapping
- 9:09Zero day for exploits
- 13:26Tesla Pwn2Own exploit
- 15:54Security vs safety in cars
- 19:31Exploitation paths
- 23:19Exposed manufacturer APIs
- 26:12Remote hacks via infotainment
- 30:32Firmware analysis
- 34:11CAN bus security flaws
- 36:18Weaponizing exploits
- 41:36Chaining vulnerabilities
- 42:18Car hacking strategies
- 45:31Q&A
related talks
31mHacking Everything – The Dark Side of the Internet of Things
37mAutomatic Automotive Hacking
41mPanel: Tackling Automotive Hardware Vulnerabilities
01h 06mHow hacking works
40mWearable Botnets and Happy Hacked Drivers
41mKeynote Presentation: Ten Years After the Jeep Hack: A Retrospective on...
36mCar Hacking
55mHow hacking works