2 ms·
Interesting in that fixing it would be difficult, as it's a documented part of the protocol. I suppose, though, manufacturers could at least focus on isolating
by tyingq 9y ago
Interesting in that fixing it would be difficult, as it's a documented part of the protocol.
I suppose, though, manufacturers could at least focus on isolating the OBD-II port from most of the CAN bus, and putting the unfirewalled CAN bus connectors in a place that's harder to get to. There seems to be a lot of variation there now. Some cars isolate at least some functions, others have the OBD-II port completely connected to everything.
- sebazzz 9y agoThe problem is not OBD-II. Rather the risk is when another vulnerability occurs on another system attached on the CAN bus like an infotainment system. If that infotainment system is vulnerable and the vulnerability allows to control the CAN bus then you have the real problem.
- tyingq 9y agoI don't see the difference. Both have no need for unfettered access to the entire CAN bus. See this for example: https://www.autoblog.com/2015/01/21/2-million-progressive-snapshot-customers-may-be-at-risk-for-car/ https://www.autoblog.com/2015/01/21/2-million-progressive-sn... OBD-II messages are a subset of CAN bus messages, identified by bits in the header, so it should be simple to filter/firewall down to just what's needed for that physical port.