Fail Harder: Finding Critical 0-Days in Spite of Ourselves
summary
Series of real-case failures that still lead to critical zero-days: pulled a flash chip, reprogrammed it and gets a root shell from serial console after crude fly-wiring; manual reballing fries a BGA and forces a different path; Netop Vision Pro and a patient monitor expose cleartext credentials and falsified vitals; an Azure Sphere chain yields remote code and $160k bounty; hitting a pre-prod claim bug lets devices be claimed twice -> $48,000 paid.
AI-written summary · about
chapters (14)
- 0:00black hat
- 1:42Patient Monitor
- 2:04Belkin Wemo Insights Plug
- 2:55Delta entilibus Building Controller
- 4:18Azure Sphere
- 5:28Clean solder work
- 6:13High-tech approach
- 10:27Slack == Project Documentation
- 15:54Brute force the password!!!
- 16:54Code is documentation....
- 24:55Fuzzing is hard
- 26:44Vendor Disclosure
- 27:48Conference Submission Feedback
- 32:22Watch out for burnout
related talks
44mCritical Zero Days Remotely Compromise the Most Popular Real-Time OS
39mNight of the living vulnerabilities
32mBreaking the Chain: Advanced Offensive Strategies in Software Supply Chain
51mExploiting Hardware Glitches And Side Channels In Perfect Software
50mPwnie Awards 2016
44mNight of the living vulnerabilities
53mFive Years of 'Make 0Day Hard'
44mExposing Critical Threats In Millions Of Connected Devices