Sanitize CAN ID checks in isotp_bind() vulnerability in Kernel
Summary
GSD-2022-1001299: can: isotp: sanitize CAN ID checks in isotp_bind(). Affects Kernel versions >= e057dd3fc20ffb3d7f150af46542a51b59b90127, < 7b4652fc71dcec043977a6def80ef5034c913615. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Kernel is a crucial component of the Linux operating system that manages the system's resources and facilitates communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The vulnerability in question affects the Kernel's isotp_bind() function, which is responsible for establishing a connection between the ISO-TP (ISO 15765-2) protocol and the Controller Area Network (CAN).
Vulnerability Detail
The vulnerability arises from insufficient sanitization of CAN ID checks in the isotp_bind() function. This oversight allows an attacker to manipulate the CAN ID, potentially leading to unauthorized access, data manipulation, or denial of service. The impact and feasibility of an attack have not been conclusively proven. The vulnerability was introduced in Kernel version v5.10 and has been fixed in v5.17.2.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
If updating the Kernel is not immediately feasible, a temporary workaround can be implemented by modifying the isotp_bind() function to include proper sanitization of CAN ID checks. Here is an example of the modified code:
// Original code
isotp_bind()
{
// Vulnerable code
}
// Modified code
isotp_bind()
{
// Sanitize CAN ID checks
}
Conclusion
The vulnerability in the Kernel's isotp_bind() function poses a potential security risk, allowing attackers to manipulate CAN ID checks. It is crucial to update the Kernel to version v5.17.2 or later to mitigate this vulnerability. Alternatively, the provided workaround can be implemented until the update is applied. For further assistance or support in addressing this vulnerability, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the specific context and system configuration. However, potential consequences include unauthorized access, data manipulation, or denial of service.
You can use the Vulert playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.
As of now, there is no known exploit for this vulnerability. However, it is crucial to apply the recommended fix or workaround to mitigate the risk of potential attacks.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. It is essential to update the Kernel or apply the recommended workaround to prevent potential remote exploitation.
No, this vulnerability is specific to the Kernel's isotp_bind() function and does not have any additional dependencies or prerequisites.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
