Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security

11/7/2019
07:30 AM
By Alex Wawro, Special to Dark Reading
By Alex Wawro, Special to Dark Reading
News
50%
50%

Black Hat Q&A: Hacking a '90s Sports Car

Security researcher Stanislas Lejay offers a preview of his upcoming Black Hat Europe talk on automotive engine computer management and hardware reverse engineering.

Communicating with your car and building your own tools is easier than you think, and well worth the effort, says Stanislas Lejay who will be briefing attendees in London at Black Hat Europe next month on Unleashing the Power of My 20+ Years Old Car. It's a fun and fascinating look at Lejay's efforts to bypass the speed limiter (set at ~180 km/h) and still pass inspection.

Lejay opens up to Dark Reading about the process, what he learned, and what Black Hat attendees can look forward to in his Briefing.

Alex: Tell us a bit about how you got into cybersecurity, and what you're currently working on.

I went to a computer engineering school in France (EPITA) and followed the normal 5-year course. However, in the middle of my second year, a senior showed me a book called "Hacking: The Art of Exploitation" that I started reading "just for fun." But as I was reading, I found it fascinating to try to think the other way around to break code, and make it do stuff it was never designed to do.

So I started learning reverse engineering and exploitation in my free time. (We didn't have any class related to that until the fourth year, if you choose the infosec specialization.) I started participating in a few capture the flag competions (CTFs), ROPing in my own code, and just trying to see how far I could go. I played with console hacking, emulation, firmwares, and eventually started working on cars.

A few years, projects and conferences later, I work as an automotive computer security engineer near Tokyo and fiddle with my own cars' engine control units (ECUs) in my spare time.

Alex: What inspired you to pitch this talk for Black Hat Europe?

Stanislas Lejay: This talk is a result of a real-life project I had going on, with a real purpose. I think that talking about a project with successes and failures, and a clear goal in sight, is the best way to actually get people interested in stuff they wouldn't bother learning about otherwise. People seemed to enjoy my last talk about "car hacking," so while writing an article about it is nice, being able to show it to an audience and exchange thoughts on the subject afterward sounds even better.

Alex: Any fun anecdotes about fiddling with your cars in Japan?

Stanislas Lejay: Well, so far it can still pass "Shaken" (the mandatory car inspection every two years) because my system doesn't modify the ECU and is basically just a bypass circuit that I can activate or not with a switch. So, in regard to the law, my car is still 100% stock but for "a few additional wires and microcontrollers." All my cars are still road-legal, so far, as it is one of my main concerns when modifying them. So no, sorry, no fun anecdote on that side!

Alex: What do you hope Black Hat attendees will get out of seeing your talk?

Stanislas Lejay: While this talk doesn't expose anything new, even less knowing that the car is 20 years old, it should still let people get an idea of how fun it is to play with cars, what you can do with them, and that most aftermarket tools you can buy for pretty high prices are not witchcraft. Communicating with your car and building your own tools for it is actually not that hard and can help you get a lot of insights, for cheap, on what's going on in your car when you actually drive it.

Get more information on Lejay’s Briefing and lots of other cutting-edge content in the Briefings schedule for Black Hat Europe, which returns to The Excel in London December 2-5, 2019. For more information on what’s happening at the event and how to register, check out the Black Hat website

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
anthonydrobbins
50%
50%
anthonydrobbins,
User Rank: Apprentice
11/8/2019 | 2:45:57 AM
thank for somuch
hihihi
The Cold Truth about Cyber Insurance
Chris Kennedy, CISO & VP Customer Success, AttackIQ,  11/7/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
Black Hat Q&A: Hacking a '90s Sports Car
Black Hat Staff, ,  11/7/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18862
PUBLISHED: 2019-11-11
maidag in GNU Mailutils before 3.8 is installed setuid and allows local privilege escalation in the url mode.
CVE-2019-18853
PUBLISHED: 2019-11-11
ImageMagick before 7.0.9-0 allows remote attackers to cause a denial of service because XML_PARSE_HUGE is not properly restricted in coders/svg.c, related to SVG and libxml2.
CVE-2019-18854
PUBLISHED: 2019-11-11
A Denial Of Service vulnerability exists in the safe-svg (aka Safe SVG) plugin through 1.9.4 for WordPress, related to unlimited recursion for a '<use ... xlink:href="#identifier">' substring.
CVE-2019-18855
PUBLISHED: 2019-11-11
A Denial Of Service vulnerability exists in the safe-svg (aka Safe SVG) plugin through 1.9.4 for WordPress, related to potentially unwanted elements or attributes.
CVE-2019-18856
PUBLISHED: 2019-11-11
A Denial Of Service vulnerability exists in the SVG Sanitizer module through 8.x-1.0-alpha1 for Drupal because access to external resources with an SVG use element is mishandled.