The Car Hacker’s Handbook A Guide for the Penetration Tester is a book about how to interface with cars to read from onboard systems, spoof devices, and control the vehicle on your own. I enjoyed this book, it is easily the best book I found on learning how to use a CAN bus.

The book starts by putting the reader in the proper mindset for exploring the security and attack paths for a given vehicle. The first chapter gets the reader thinking about all (most) of the ways that you can interface with a vehicle to hack it and specific suggestions about how to approach each of those. He describes various ways of rating threats. One of them being DREAD. DREAD is a formal way of assessing threats with a focus on malicious intent (which other rating systems often ignore). When I first read about DREAD I thought he was going to start rating systems with the Harry Potter grading system of Outstanding, Exceeds Expectations, Acceptable, Poor, Dreadful and Troll. This section has two uses; if you modify systems it will help you figure out how to get access to a vehicle, if you build systems it will help you think about securing what you build.

Some of the buses that you should be prepared to find discussed in this book and in cars are:

• CAN (Low-speed LS-CAN, mid-speed MS-CAN, high-speed HS-CAN)
• CANopen
• GMLAN
• SAE J1850
• PWM
• VPW
• Keyword
• ISO 9141-2
• LIN
• MOST
• FlexRay
• Automotive Ethernet (& AVB)

I had no idea there were that many protocols in use and I have only heard of 2/3 of them!

The book introduces a bunch of tools for working with CAN buses, I have never used some of them but they are opensource Linux tools that seem to have nice features. I will definitely check them out next time I am working with a CAN bus. There is also an appendix at the end of the book that discusses many tools ranging from hobby level to professional. This follows up with some really basic writing of CAN drivers in Linux and how to communicate with your vehicle (the book calls it weaponizing, I guess it sounds good but I would call it using what you know to get stuff done).

Importantly, this book discusses what to do if you get into different fault conditions. For example:

• Flashing lights
• Car not turning on
• Car not turning off
• Vehicle responding recklessly
• Bricking your car !!!***@@@@##!!

That list above can be scary and the author gives some advice for handling them, however, it might have been nice if the author spent more time discussing the potential faults and how to avoid them (particularly, how not to brick your car!).

It is good to hear that most engine control units (ECU’s) have some sort of tamper protection so you can not change its firmware. However, the author does note that some of those protections are laughably weak. There are a few chapters on understating common ECU protocols, how to simulate them, and how to attack them. This is probably above what most robotic integrations would do, however, I have worked on projects where we removed an ECU and replaced it with our own that we could configure; so this is still a good topic to read. It also has some content that is good for generic embedded systems that are not covered in most embedded systems books.

One thing this book lacks is details about specific car models. I like that the core of the book is not manufacturer dependent but it would be nice to have more information about CAN codes, protocol information, pinouts, ECU configurations, etc. I think some of that high-level information might be good as an appendix, with the full expanded set of documentation as web content for readers.

This book has a good description of applied CAN hardware as well as the protocol. This is what I wish I was able to read when I first started working with CAN buses. I give this book 5 out of 5. It has really good practical knowledge for hacking your vehicle without going into a lot of theory. I would recommend this book for engineers working with embedded systems, even if they do not work with cars. I think that Smith wrote a boot about how to do stuff; which had the unintended consequence of making a great book for learning how to actually work with real systems.

After reading this book I really want to go sniff my vehicles buses and see what I can find.

I would like to thank No Starch Press for providing me with a hard copy of this book for review.

Disclaimer: I have never met the author of this book and the opinions above are mine.

The post Book Review: The Car Hacker’s Handbook by Craig Smith appeared first on Robots For Roboticists.