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.

Vulnerabilities / Threats

9/2/2016
09:00 AM
Connect Directly
Facebook
Twitter
RSS
E-Mail
50%
50%

Researchers Uncover Car Infotainment Vulnerability

Should an automobile manufacturer have to release a patch for a feature that they never deployed? A newly discovered vulnerability in MirrorLink's infotainment software may force an answer.

A newly uncovered vulnerability in the MirrorLink infotainment software is forcing lots of hard questions about who's ultimately responsible for security in the automobile supply chain.

Damon McCoy, an assistant professor of computer science and engineering at NYU's Tandon School of Engineering, and a group of students at George Mason University found vulnerabilities in MirrorLink, a standard tool for connecting smartphones to in-vehicle infotainment (IVI) systems. Some carmakers disable MirrorLink because they use a different standard or because their version of MirrorLink is a prototype that can be activated later.

MirrorLink was created in 2011 and is overseen by the Car Connectivity Consortium (CCC), which represents 80% of the world's automakers. It's the first industry standard for smartphones-IVI connectivity; Apple has since deployed CarPlay and Google has Android Auto.

"Tuners," a segment of the OEM market that customizes automobiles, are able to activate MirrorLink, thanks to a helpful YouTube instructional video that's already logged more than 60,000 views, according to McCoy. Once active, MirrorLink then allows drivers to use the apps on their IVI -- the touchscreen, audio speakers, and the in-car microphone. "Drivers get improved functionality," McCoy says. "This is something tuners do all the time."

Unfortunately, this tuner activation of MirrorLink also renders the car vulnerable to access by third-parties, who could then mess with the software for the anti-lock braking system, for example, or other critical safety features. The vulnerability was detailed in a paper presented at last month's USENIX Workshop on Offensive Technologies in Austin, Texas. The research was funded by General Motors, the National Science Foundation, and the Department of Homeland Security.

So far, McCoy and his fellow researchers haven't publicly identified the carmaker or the OEM/tuner but are in contact with them. "We don't want to name and shame … it's likely a systemic problem," he said, since manufacturers normally sell to multiple OEMs.

Alan Ewing, president of the CCC, said the group has just begun its analysis of the vulnerability. "The question coming up as we go through the paper is whether this is a vulnerability of MirrorLink proper, or a bad implementation by an auto OEM that left open and stripped out security information that made the hack possible," Ewing says.

While emphasizing that CCC takes security extremely seriously, there is no patch planned for MirrorLink at present, he says.

"We're always about improving, so if there's something that needs fixing in the MirrorLink implementation, we'll close that gap," Ewing says. "But at the end of the day, if it avoids our certification, is implemented incorrectly, and exposes some bad code, we can't prevent that kind of misuse."

The vulnerability and the auto industry's complex supply chain muddy the issue of who's responsible for security or issuing a fix. "Does the manufacturer have to release a patch for a feature that they never deployed?" McCoy says. The answer isn't clear-cut.

One of the researchers' recommendations was for the auto industry to quarantine apps for cars in the same way that apps are confined or isolated with smartphones. "Ideally, the OEMs could build similar sandbox containment technology for these apps," McCoy says.

Regardless of the fix, there needs to be some sort of industry gatekeeper that leverages those further down the supply chain to build secure systems from the start and correct vulnerabilities as they're found, McCoy adds. "I don't know if that means the CCC needs to audit suppliers who use MirrorLink, just as Apple and Google audit suppliers to make sure they all conform to standards for security," he says. And if they find that one of them skips some of the security measures, they should say it doesn't confirm to the protocol.

Related Content:

 

Terry Sweeney is a Los Angeles-based writer and editor who has covered technology, networking, and security for more than 20 years. He was part of the team that started Dark Reading and has been a contributor to The Washington Post, Crain's New York Business, Red Herring, ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
FluBot Malware's Rapid Spread May Soon Hit US Phones
Kelly Sheridan, Staff Editor, Dark Reading,  4/28/2021
Slideshows
7 Modern-Day Cybersecurity Realities
Steve Zurier, Contributing Writer,  4/30/2021
Commentary
How to Secure Employees' Home Wi-Fi Networks
Bert Kashyap, CEO and Co-Founder at SecureW2,  4/28/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-22675
PUBLISHED: 2021-05-07
The affected product is vulnerable to integer overflow while parsing malformed over-the-air firmware update files, which may allow an attacker to remotely execute code on SimpleLink Wi-Fi (MSP432E4 SDK: v4.20.00.12 and prior, CC32XX SDK v4.30.00.06 and prior, CC13X0 SDK versions prior to v4.10.03, C...
CVE-2021-22679
PUBLISHED: 2021-05-07
The affected product is vulnerable to an integer overflow while processing HTTP headers, which may allow an attacker to remotely execute code on the SimpleLink Wi-Fi (MSP432E4 SDK: v4.20.00.12 and prior, CC32XX SDK v4.30.00.06 and prior, CC13X0 SDK versions prior to v4.10.03, CC13X2 and CC26XX SDK v...
CVE-2020-14009
PUBLISHED: 2021-05-07
Proofpoint Enterprise Protection (PPS/PoD) before 8.17.0 contains a vulnerability that could allow an attacker to deliver an email message with a malicious attachment that bypasses scanning and file-blocking rules. The vulnerability exists because messages with certain crafted and malformed multipar...
CVE-2021-21984
PUBLISHED: 2021-05-07
VMware vRealize Business for Cloud 7.x prior to 7.6.0 contains a remote code execution vulnerability due to an unauthorised end point. A malicious actor with network access may exploit this issue causing unauthorised remote code execution on vRealize Business for Cloud Virtual Appliance.
CVE-2021-26122
PUBLISHED: 2021-05-07
LivingLogic XIST4C before 0.107.8 allows XSS via feedback.htm or feedback.wihtm.