Panel: Tackling Automotive Hardware Vulnerabilities
summary
Cars resemble IoT stacks: outdated infotainment exposes infotainment Android exploits, firmware extraction tools routinely pull ECU images, and closed supplier binaries prevent proper review. Remote attacks persist — key fobs suffer relay/distance-bounding bypass and attackers exploit open JTAG to remove paid-feature locks, enabling mass modding. AI causes new failure modes (stickers fool vision stacks), V2V messaging and HSM usage add complexity, standards lag, and the practical fix is secure-by-design threat models, pen testing of supplier firmware, and tracking firmware versions.
AI-written summary · about
chapters (14)
- 0:00Introduction and panel setup
- 1:14Common automotive hardware vulnerabilities
- 3:19Balancing safety and security
- 6:38Safety maturity vs security standards
- 9:18Regulatory challenges and delays
- 13:09Cryptography implementation flaws
- 13:31Policies for third-party vendor security
- 16:38Vendor compliance and standards
- 21:10Role of AI in hardware security
- 24:46Future automotive hardware attacks
- 27:12RF attacks on key fobs
- 29:19Advice for startups in automotive security
- 34:39Ethics of automotive security research
- 37:48Researchers as heroes or villains
related talks
20mSecurity and Safety in the Modern Vehicles
21mIndustrial IoT security issues and countermeasures
43mSecuring the Connected Car
37mAutomatic Automotive Hacking
43mSecuring Software-Defined Vehicles: From Threat Awareness To Holistic Cybersecur...
51mSteering Clear of Danger: Decrypting the Realities of Remote Car Hacking
40mSecuring the Connected Car
41mKeynote Presentation: Ten Years After the Jeep Hack: A Retrospective on...