FORENSIC LEGIBILITY EXAMINER
CASE 079CONTROLLED ACCESS & AUTHORIZATION2026-02-28DISPOSITION: INTERNET-FACING SYSTEM BRIDGING TO SAFETY-CRITICAL CONTROLS WITHOUT ENFORCED SEGMENTATIONARCHIVE →

Vehicle Control System Access Authority Failure Through Internet-Connected Infotainment Bridging to Safety-Critical Networks at FCA Uconnect

When a vehicle's network architecture places an internet-connected entertainment system on a network path that reaches the bus controlling steering, braking, and transmission — and the internal vehicle network protocol accepts any properly formatted message without authenticating its source — an attacker who compromises the entertainment system can issue commands to safety-critical vehicle controls. The segmentation between the entertainment domain and the vehicle control domain existed as an architectural assumption: these are different systems serving different functions. The assumption was not enforced as a boundary. The internet connectivity existed by design. The path from internet connectivity to the braking system existed as a consequence of that design. The access control that should have prevented one from reaching the other did not exist as an enforced constraint.
Failure classification: Assumed Network Domain Separation Without Enforced Boundary Between Internet-Facing and Safety-Critical Systems

Context

Modern vehicles contain dozens of electronic control units communicating over internal networks — primarily the CAN bus protocol developed by Bosch in 1983 for reliable, real-time communication between vehicle subsystems. CAN was designed for an isolated environment where every device on the bus was trusted because every device was installed by the manufacturer. The protocol includes no source authentication — any device on the bus can send any message, and receiving devices accept and act on messages based solely on the message identifier, not on the identity of the sender.

As vehicles added internet-connected features — navigation, streaming audio, over-the-air updates, remote start via smartphone apps — the infotainment systems providing these features were connected to external networks. In the 2014 Jeep Cherokee, the Uconnect infotainment system connected to the Sprint cellular network, providing internet access to the head unit. The head unit was also connected, through the vehicle's internal architecture, to the CAN bus that carried messages between the engine control unit, the transmission controller, the electronic braking system, and the electric power steering module. The internet-connected system and the safety-critical control systems shared a network path.

Trigger

In July 2015, security researchers Charlie Miller and Chris Valasek publicly demonstrated that they could remotely compromise a Jeep Cherokee driven by a journalist on a highway. Working from a laptop miles away, they connected to the vehicle's Uconnect system through the Sprint cellular network, exploited a vulnerability in the head unit's software to gain code execution, pivoted from the infotainment system to the CAN bus, and issued commands to the vehicle's safety-critical systems. They demonstrated control of the air conditioning, radio, and windshield wipers, then — with the driver's prior consent — disabled the transmission while the vehicle was traveling at highway speed on an active freeway.

The demonstration was not theoretical. The researchers controlled the vehicle remotely, in real time, while it was being driven. They could manipulate steering at low speeds, disable brakes, and kill the engine. The attack required no physical access to the vehicle — only knowledge of its IP address on the Sprint network, which was discoverable. Any of the approximately 1.4 million FCA vehicles equipped with vulnerable Uconnect systems could potentially be targeted remotely by anyone who could reach the vehicle's network address.

Failure Condition

The vehicle's network architecture treated the infotainment domain and the vehicle control domain as functionally separate — different systems, different purposes, different engineering teams. This functional separation was not enforced as a network boundary. The infotainment system could reach the CAN bus because the architecture included a communication path between them — needed for features like displaying vehicle diagnostics on the dashboard screen or allowing the infotainment system to send commands for convenience functions. That communication path did not enforce directional constraints or message-type restrictions that would have prevented a compromised infotainment system from sending arbitrary CAN messages to safety-critical controllers.

The CAN bus compounded the architectural failure. Because CAN was designed for a trusted, isolated environment, it had no mechanism to authenticate message sources. A braking command sent by the electronic braking controller looked identical on the bus to a braking command sent by the compromised infotainment system. The safety-critical controllers had no way to determine whether a message originated from a legitimate source or from an attacker who had entered the network through the internet-connected entertainment system. The authorization to connect the vehicle to the internet existed. The segmentation that should have prevented that connectivity from reaching the braking system did not exist as an enforced control.

Observed Response

FCA recalled 1.4 million vehicles — the first cybersecurity-motivated recall in U.S. automotive history. Sprint blocked the network port used in the attack. The National Highway Traffic Safety Administration opened an investigation and subsequently issued cybersecurity best practices for the automotive industry. The demonstration catalyzed the automotive cybersecurity field, contributing to the development of ISO/SAE 21434 (road vehicle cybersecurity engineering) and UNECE WP.29 regulations requiring cybersecurity management systems for vehicle type approval. The CAN bus authentication gap — a protocol designed for a pre-internet vehicle architecture, now deployed in vehicles connected to the internet — remained a fundamental design challenge for the industry.

Analytical Findings

References
  1. 1. Miller, Charlie and Valasek, Chris, "Remote Exploitation of an Unaltered Passenger Vehicle," Black Hat USA, August 2015.
  2. 2. Greenberg, Andy, "Hackers Remotely Kill a Jeep on the Highway — With Me in It," Wired, July 21, 2015.
  3. 3. National Highway Traffic Safety Administration, recall campaign 15V-461, FCA Automobiles, July 2015.
  4. 4. ISO/SAE 21434:2021, "Road Vehicles — Cybersecurity Engineering."
  5. 5. UNECE WP.29, Regulation No. 155 on Cyber Security and Cyber Security Management System, January 2021.