There are multiple vulnerabilities in the Mazda Connect Connectivity Master Unit (CMU) system installed in multiple car models, such as the Mazda 3 model year 2014-2021, according to a report with Zero Day Initiative.

Like in so many cases, these vulnerabilities are from insufficient sanitization when handling attacker-supplied input. A physically present attacker could exploit these vulnerabilities by connecting a specially crafted USB device – such as an iPod or mass storage device – to the target system, according to the report written by Dmitry Janushkevich. Successful exploitation of some of these vulnerabilities results in arbitrary code execution with root privileges.

Visteon manufactured the e specific CMU unit that was the target of the research. Johnson Controls Inc (JCI) initially developed the software. The research ended up conducted against the latest available software version (74.00.324A). Earlier software versions down to at least 70.x may also suffer from these vulnerabilities.

CMU Receives Software ‘Tweaks’
In this case, the CMU has a very active “modding scene” with the community releasing multiple software “tweaks” to alter the operation of the unit.

While there are multiple vulnerabilities, exploitation of the OS command injection vulnerabilities is relatively straightforward. All the attacker needs to do is create a file on a FAT32-formatted USB mass storage device where the name will contain the OS commands to end up executed.

Schneider Bold

The filename must end with .up for the software update handling code to recognized it. While all three command injection vulnerabilities end up exploited via the file name, the easiest one to exploit is by far the ZDI-CAN-23420 as there are no specific exploitation requirements such as validity of the crafted update file.

Exploitation of the described command injection vulnerabilities can further facilitate by the fact software update installation can trigger automatically upon connecting a USB mass storage device; this is a “known feature” activated by simply placing an empty file named jci-autoupdate on the storage device.

Once the initial compromise ends up achieved, the attacker can gain persistence through manipulation of the root file system, such as installing backdoored system components which will persist across system restarts.

Furthermore, the attacker can move laterally and install a specially crafted VIP microcontroller software allowing unfettered access to vehicle networks, potentially impacting vehicle operation and safety.

Attack Chain
In the lab environment, the entire attack chain – from plugging in a USB drive to installing a crafted update on the VIP – takes only a few minutes. Currently, there is no reason to believe a similar attack will take significantly more time against a unit installed in a car. This means the vehicle can end up compromised while a valet is handling it, during a ride share, or via USB malware. Naturally, the same can occur in a shop environment where there are no significant time pressures.

The CMU can end up compromised and “enhanced” to, for example, attempt to compromise any connected device in targeted attacks that can result in DoS, bricking, ransomware, safety compromise, etc.

This research effort and its output highlighted the fact that high-impact vulnerabilities can occur even in a very mature automotive product that has been on the market for a number of years and with a long history of security fixes, according to the report. To date, these vulnerabilities remain unpatched.

“Injection is everywhere. Every piece of data could contain an attack targeting any downstream systems that use that data,” said Jeff Williams, founder and CTO of Contrast Security. “In theory, Mazda developers should have known that the serial numbers pulled from an iPhone can’t end up trusted and shouldn’t go directly into SAL queries. But the real world is much more complex. Maybe the developers writing the code to store those serial numbers had no way of knowing they came from the user or weren’t validated. Mazda should use runtime security testing to ensure they can track untrusted data and help developers use it safely.”

Click here for more on the report.

Pin It on Pinterest

Share This