Bluetooth: SMP: Fail if remote and local public keys are identical
Summary
GSD-2021-1000525: Bluetooth: SMP: Fail if remote and local public keys are identical. Affects Kernel versions >= bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9, < 4555cee33f7d75c1ee69902c872c9d1e9568ebd5. 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 vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of the operating system that manages system resources and provides an interface for software to interact with the hardware. It plays a crucial role in the functioning of the entire system. The vulnerability specifically impacts the Bluetooth Secure Simple Pairing (SMP) protocol, which is used for establishing secure connections between Bluetooth devices. The vulnerability allows an attacker to exploit the failure of the SMP protocol to reject connections when the remote and local public keys are identical.
Vulnerability Detail
The vulnerability arises from a flaw in the SMP protocol implementation. When the remote and local public keys are identical, the protocol fails to reject the connection, potentially allowing an attacker to establish a malicious connection with a Bluetooth device. The impact of this vulnerability could vary depending on the context and the capabilities of the affected device. It could potentially lead to unauthorized access, data leakage, or other malicious activities. The vulnerability was introduced in version v3.17 of the Linux Kernel and has been fixed in version v4.14.234.
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
There is no specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the Kernel package's Bluetooth SMP protocol implementation allows an attacker to establish a malicious connection when the remote and local public keys are identical. This can lead to unauthorized access, data leakage, or other malicious activities. It is recommended to update the Linux Kernel to version v4.14.234 or later to fix the vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could vary depending on the context and the capabilities of the affected device. It could potentially lead to unauthorized access, data leakage, or other malicious activities.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the playground will provide real-time alerts for open-source vulnerabilities.
Yes, the vulnerability has been fixed in version v4.14.234 of the Linux Kernel. It is recommended to update to this version or a later one to address the issue.
Yes, this vulnerability can be exploited remotely by an attacker who can establish a malicious connection with a Bluetooth device.
There are no known instances of this vulnerability being exploited in the wild. However, it is important to apply the necessary updates to mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
