On January 26th, the research group at Qualys, an IT security provider, published a report illustrating how they succeeded to exploit a vulnerability (CVE-2021-3156) in Sudo, an open source code program that is widely used in Linux-based systems. This blog will tell you a little bit more about the vulnerability and Argus’ recommendations.
Why Are We Bringing This Vulnerability to Your Attention?
The vulnerability, which exists in Sudo versions since 2011, potentially impacts newly introduced Linux-based ECUs, such as TCUs, ADAS systems, infotainment systems, instrument clusters, and smart gateways and could affect 10s of millions of vehicles.
What Harm Can the Vulnerability do if Exploited?
The vulnerability, also known as Baron Samedit, is a heap overflow vulnerability that can enable privilege escalation. Privilege escalation vulnerabilities provide unauthorized users administrative rights to the Linux system, enabling them to take full control of potential target ECUs. However, it is important to note that this vulnerability on its own DOES NOT PRESENT HIGH RISK to automakers as malicious actors still require initial code execution access to the ECU in order to exploit it.
In the event of compromise and without specific security mechanisms in place, an exploit of this vulnerability could enable access to safety critical components. Even in secured architectures, the vulnerability may enable vehicle tracking, access to sensitive data, and Denial of Service of the target ECU.
What Should Vehicle Manufacturers Do?
The first thing that vehicle manufacturers should do is determine if this vulnerability affects your ECUs and if so, which ECUs. Once you understand your risk exposure, you can determine if you need to initiate a mitigation plan.
With this in mind, protecting APIs is becoming extremely important in the IT world, and ultimately, in the automotive industry which relies on advanced technologies. To start, automotive CISOs and fleet managers need to look beyond standard risk assessments and penetration tests and add an additional layer of protection around connected car services.
Because this is most likely not the last time that a vulnerability of this nature will be exposed, preventative security mechanisms should be introduced into new ECUs.
Argus Connected ECU Protection includes independent modules that work individually, or together, to help vehicle manufacturers prevent a wide range of exploits, including exploits like this one, from targeting connected ECUs. The solution also helps vehicle manufacturers comply with regulations and standards like UNECE UNR 155 (WP. 29).
To learn more about how public CVEs like this one can impact vehicle manufacturers and the most efficient mitigation approach, get a copy of our technical white paper, Navigating Public CVEs in the Automotive Domain here.
For more information about the vulnerability, see Qualy’s blog.