Welcome Guest. | Log In | Register | Membership Benefits

Car Systems Reminiscent Of Early PCs

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

Sep 08, 2011 | 04:51 PM | 

By Robert Lemos, Contributing Editor
Dark Reading


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.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS












Featured Webcasts
Featured Whitepapers
Featured Reports
Bugs
ENTERPRISE VULNERABILITIES
Vulnerability:ssl-vpn end-point interrogator/installer activex control
Published:2010-11-03
Severity:High
Description:Stack-based buffer overflow in SonicWALL SSL-VPN End-Point Interrogator/Installer ActiveX control (Aventail.EPInstaller) before 10.5.2 and 10.0.5 hotfix 3 allows remote attackers to execute arbitrary code via long (1) CabURL and (2) Location arguments to the Install3rdPartyComponent method.
Vulnerability:gvim
Published:2010-11-03
Severity:High
Description:Untrusted search path vulnerability in VIM Development Group GVim before 7.3.034, and possibly other versions before 7.3.46, allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse User32.dll or other DLL that is located in the same folder as a .TXT file. NOTE: some of these details are obtained from third party information.
Vulnerability:cforms
Published:2010-11-03
Severity:Medium
Description:Multiple cross-site scripting (XSS) vulnerabilities in wp-content/plugins/cforms/lib_ajax.php in cforms WordPress plugin 11.5 allow remote attackers to inject arbitrary web script or HTML via the (1) rs and (2) rsargs[] parameters.
Vulnerability:links, wsn links, wsn links
Published:2010-11-03
Severity:High
Description:Multiple SQL injection vulnerabilities in search.php in WSN Links 5.0.x before 5.0.81, 5.1.x before 5.1.51, and 6.0.x before 6.0.1 allow remote attackers to execute arbitrary SQL commands via the (1) namecondition or (2) namesearch parameter.
Vulnerability:deluxebb
Published:2010-11-03
Severity:Medium
Description:SQL injection vulnerability in misc.php in DeluxeBB 1.3, and possibly earlier, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the xthedateformat parameter in a register action, a different vector than CVE-2005-2989, CVE-2006-2503, and CVE-2009-1033.



Briefing Centers
POWERFUL INFORMATION
AT YOUR FINGERTIPS
(SPONSORED LINKS)