Vulnerabilities / Threats
1/12/2011
10:55 AM
Connect Directly
RSS
E-Mail
50%
50%

Schwartz On Security: Hack My Ride

Car security exploits are fast, cheap, and out of control. Why don't automotive manufacturers do more to secure their vehicles?

What do car immobilizers, remote tire pressure gauges, and wireless car-key fobs have in common? Beyond the obvious automotive angle, they've all been hacked using relatively low-cost exploits.

Take car immobilizers and keyless entry systems. A group of Swiss researchers from ETH Zurich recently demonstrated an attack -- dubbed the Autoknacker in Swiss German -- against 10 recent car models from eight different manufacturers, all of which use passive keyless entry and start (PKES). Under this system, a key fob only needs to be physically near the car to deactivate the immobilizer, open the doors, and start the engine.

Here's where attackers come in: By using a pair of wireless antennas, they can rebroadcast the key fob's signal in nanoseconds to fool the car into thinking the driver is present. Furthermore, the antenna picking up the key fob's signal needs to be within only 8 meters (26 feet) of it, making the attack difficult to detect.

The Swiss researchers tested two attack scenarios. First, when a driver is in the supermarket, key fob in his pocket. Second, when the key is left inside a house -- but within range of the antenna -- and the car is parked outside. Using the two-antenna approach, all 10 cars were successfully hacked and driven away.

The total cost for the wireless attack, not including graduate students, ranged from $100 to $1,000, depending on the quality of the hardware used. Interestingly, the cryptography used to secure the fob-to-car communications didn't matter. The researchers were able to remotely fool all 10 cars simply by rebroadcasting the signal.

To block such attacks, the researchers suggest that car manufacturers add security checks to confirm that the key really is located next to the car. "I don't see a way around it," said research lead Srdjan Capkun, an assistant professor of computer science in the system security group at ETH Zurich, quoted in MIT's Technology Review. His group is working on new approaches to help.

While the Swiss researchers' attack doesn't require cracking the encryption keys used to secure the fob-to-car communications, that's also an option. According to New Scientist, security researchers have cracked the keys used by multiple types of key fobs, including the Hitag 2 encryption key from NXP Semiconductors present in many recent cars, although that isn't the only one that's been hacked.

"The proprietary encryption keys used to transmit data between the key fob, receiver, and engine are so poorly implemented on some cars that they are readily cracked," Ari Juels of RSA Labs told New Scientist. Notably, only a few car manufacturers use 128-bit Advanced Encryption Standard (AES) keys. The rest use 40- or 48-bit keys, which security experts now regard as ineffective. Semiconductor makers report that they already have stronger approaches, but it's difficult to convince car manufacturers to use them.

Ditto for wireless car tire pressure gauges. Last year, researchers found that the wireless networks built into many cars in the past three years don't perform authentication or input validation. Researchers thus found it easy to spoof a variety of inputs, such as sensor messages indicating a tire pressure failure. According to the researchers, "we validated this experimentally by triggering tire pressure warning messages in a moving vehicle from a customized software radio attack platform located in a nearby vehicle."

What's the end result of poor automotive information security practices? The next time you finish grocery shopping and find that your car's gone, you can ask: Was it the car crypto -- or lack thereof -- that did you in? Unless a Swiss PhD candidate is lurking in the parking lot, the answer is, probably not. When it comes to bang for buck, there are easier attacks.

But wouldn't it be nice if car manufacturers properly secured their vehicles, so that every new convenience or feature doesn't add another information security attack vector?

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2963
Published: 2014-07-10
Multiple cross-site scripting (XSS) vulnerabilities in group/control_panel/manage in Liferay Portal 6.1.2 CE GA3, 6.1.X EE, and 6.2.X EE allow remote attackers to inject arbitrary web script or HTML via the (1) _2_firstName, (2) _2_lastName, or (3) _2_middleName parameter.

CVE-2014-3310
Published: 2014-07-10
The File Transfer feature in WebEx Meetings Client in Cisco WebEx Meetings Server and WebEx Meeting Center does not verify that a requested file was an offered file, which allows remote attackers to read arbitrary files via a modified request, aka Bug IDs CSCup62442 and CSCup58463.

CVE-2014-3311
Published: 2014-07-10
Heap-based buffer overflow in the file-sharing feature in WebEx Meetings Client in Cisco WebEx Meetings Server and WebEx Meeting Center allows remote attackers to execute arbitrary code via crafted data, aka Bug IDs CSCup62463 and CSCup58467.

CVE-2014-3315
Published: 2014-07-10
Cross-site scripting (XSS) vulnerability in viewfilecontents.do in the Dialed Number Analyzer (DNA) component in Cisco Unified Communications Manager allows remote attackers to inject arbitrary web script or HTML via an unspecified parameter, aka Bug ID CSCup76308.

CVE-2014-3316
Published: 2014-07-10
The Multiple Analyzer in the Dialed Number Analyzer (DNA) component in Cisco Unified Communications Manager allows remote authenticated users to bypass intended upload restrictions via a crafted parameter, aka Bug ID CSCup76297.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.