Vulnerabilities / Threats

Car Systems Reminiscent Of Early PCs

A lack of security scrutiny leads automobile makers to make simple, familiar security mistakes

Today's automobiles are controlled by dozens to hundreds of electronic control units (ECUs) -- embedded controllers connected by different data buses to monitor and control every aspect of a motor vehicle.

While security is taken into consideration by the car manufacturers, the companies have lacked the constant security scrutiny that has benefited -- though some software makers might say "plagued" -- the computer industry. The recent scrutiny has led to the reporting of vulnerabilities and a steady stream of academic papers on the exploitation of automotive control systems.

"No one has really attacked these systems, so there are simple secure programming techniques used in the PC world that are not yet implemented in the embedded world," says Stefan Savage, a professor of computer science and engineering at the University of Southern California at San Diego (UCSD) and author of one recent paper.

It should come as no surprise, then, that more traditional computer security firms see a market. On Wednesday, McAfee and embedded-software maker Wind River released a report surveying research into the security of information control systems in automobiles. In February, the subsidiaries of McAfee and Wind River announced a partnership to bring McAfee's security expertise to bear on embedded systems, including automotive applications.

"We were really struck at how fast embedded devices are being connected in the world," says Tim Fulkerson, senior director of marketing for McAfee Embedded Security. "Cars are really one of the more visible instances of where we encounter embedded systems in real life."

Both companies are subsidiaries of chipmaker Intel, which got its start in the PC world, but which is seeing a greater proportion of income from embedded systems. In its latest quarter, the company saw the revenue of its embedded and communications group jump by 25 percent.

Embedded automotive systems need a good security review, similar to PC software a decade ago and industrial control systems a few years ago. At the USENIX Security Conference in August, for example, researchers from the University of California at San Diego and the University of Washington revealed (pdf) that they had found a number of ways of compromising a car's systems to gain complete control over the vehicle.

In one attack, a compact disc carrying a program masquerading as a song file could exploit a car's entertainment system and, from there, take control of the vehicle. Other attacks involved using Bluetooth or cellular vulnerabilities in the automobile's network interfaces to similarly take control of systems. Because devices typically trust other embedded systems on the same communication bus, or controller area network (CAN), compromising one system leads to total compromise.

"The car industry has been taking security seriously as they build technology into cars, [but] it's really not car companies' bread and butter to know how to solve various hacks," Fulkerson says.

Embedded systems in cars do not have the benefit of secure programming techniques, address space layout randomization (ASLR), or data execution protection (DEP), which are now common in PC and mobile systems. Combine the lack of historical scrutiny with the fact that a luxury car has some 70 electronic control units and tens of millions of lines of code, and it's a recipe for continued vulnerability.

UCSD's Savage downplayed the current impact of such vulnerabilities, saying the group's research is less an imminent danger and more of a wake-up call.

"The average person doesn't have to worry about this right now -- this James Bond stuff -- no one is doing that," he says. "The place where there is more concern is when you are talking about the surveillance and espionage types of questions."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Russia Hacked Clinton's Computers Five Hours After Trump's Call
Robert Lemos, Technology Journalist/Data Researcher,  4/19/2019
Tips for the Aftermath of a Cyberattack
Kelly Sheridan, Staff Editor, Dark Reading,  4/17/2019
Why We Need a 'Cleaner Internet'
Darren Anstee, Chief Technology Officer at Arbor Networks,  4/19/2019
Register for Dark Reading Newsletters
White Papers
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-04-23
The Siemens R3964 line discipline driver in drivers/tty/n_r3964.c in the Linux kernel before 5.0.8 has multiple race conditions.
PUBLISHED: 2019-04-23
The Linux kernel before 5.1-rc5 allows page->_refcount reference count overflow, with resultant use-after-free issues, if about 140 GiB of RAM exists. This is related to fs/fuse/dev.c, fs/pipe.c, fs/splice.c, include/linux/mm.h, include/linux/pipe_fs_i.h, kernel/trace/trace.c, mm/gup.c, and mm/hu...
PUBLISHED: 2019-04-23
Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent.
PUBLISHED: 2019-04-23
Google TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local).
PUBLISHED: 2019-04-23
VVX products using UCS software version 5.8.0 and earlier with Better Together over Ethernet Connector (BToE) application version 3.8.0 and earlier uses hard-coded credentials to establish a connection between the host application and device.