From Bugs to Breaches
summary
Shows a concrete pipeline: static analysis with Cppcheck and MISRA checks followed by CAN-bus runtime fuzzing, plus a simple ECU test harness built from commodity adapters. Claims the process turns low-severity memory or input-validation bugs into exploit paths, finding six safety-critical bugs across two test vehicles and one reachable breach that disables remote locking. Includes checklist of required lab gear, test cases used, and the exact mitigation steps that stop each exploit.
AI-written summary · about
related talks
29mEvent-based Fuzzing, Patch-based Research, and Comment Police: Finding Bugs Through a Bug
57mFinding, Managing, Preventing Vulnerabilities: An Automotive Perspective
45mFinding Vulnerabilities through Static Analysis and Scripting
01h 05mTheory and Security
37mAutomatic Automotive Hacking
01h 03m“Secure Coding Best Practices: Your First Line Is The Last Line Of Defense (2 of 2)”
36mCar Hacking
01h 26mEmbracing an Adversarial Mindset for C++ Security