HomeLatest ThreadsGreatest ThreadsForums & GroupsMy SubscriptionsMy Posts
DU Home » Latest Threads » Forums & Groups » Main » General Discussion (Forum) » HACKING A CAR Is Way Too ... » Reply #2
In the discussion thread: HACKING A CAR Is Way Too Easy [View all]

Response to Segami (Original post)

Tue Jun 25, 2013, 02:36 PM

2. Hacking brakes, engines and more! -- proof of concept for auto security

http://www.popsci.com/cars/article/2010-05/researchers-hack-car-computers-shutting-down-brakes-engine-and-more

Proof-of-Concept CarShark Software Hacks Car Computers, Shutting Down Brakes, Engines, and More

Using homemade software and a standard computer port, a team of scientists has figured out exactly how easy it is to hack into a modern car -- scary news for motorists already wary of faulty brake and accelerator systems.
The research team wrote code that allows them to turn off the brakes in a moving car, change the speedometer reading, blast hot air or music on the radio, and lock passengers inside the car, PCWorld reports.

The team, led by Stefan Savage, an associate professor with the University of California-San Diego, and Tadayoshi Kohno of the University of Washington, will report on their findings in
a paper to be presented at a security conference next week.

While hacking modern-day autos is nothing new, the team's work is meant to encourage the auto industry to highlight security as it develops new computer systems. As the researchers note, many computer systems were designed to increase security -- think anti-lock brakes.

"It is not clear whether vehicle manufacturers have anticipated in their designs the
possibility of an adversary," the paper says.

Reply to this post

Back to OP Alert abuse Link to post in-thread

Always highlight: 10 newest replies | Replies posted after I mark a forum
Replies to this discussion thread
Arrow 2 replies Author Time Post
Segami Jun 2013 OP
REP Jun 2013 #1
LineNew Reply Hacking brakes, engines and more! -- proof of concept for auto security
nashville_brook Jun 2013 #2
Please login to view edit histories.