Bluetooth: SMP: Fail if remote and local public keys are identical
Summary
GSD-2021-1000524: Bluetooth: SMP: Fail if remote and local public keys are identical. Affects Kernel versions >= bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9, < 30126d4ba73119565f1748b116b9869ac6bbda6b. 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 Linux operating system, responsible for managing system resources and providing an interface for software to interact with the hardware. It plays a crucial role in the overall stability and security of the system. The vulnerability specifically impacts the Bluetooth Secure Simple Pairing (SMP) protocol, which is used for establishing secure connections between Bluetooth devices. The vulnerability arises when the remote and local public keys used in the pairing process are identical.
Vulnerability Detail
The vulnerability in the Bluetooth SMP protocol occurs when the remote and local public keys used for pairing are the same. This can lead to potential security risks as it undermines the integrity of the pairing process. An attacker could exploit this vulnerability to perform a man-in-the-middle attack, intercepting and tampering with the communication between the Bluetooth devices. The impact and attack plausibility of this vulnerability have not been proven yet, but it is essential to address it to ensure the security of Bluetooth connections.
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 Bluetooth SMP protocol, which occurs when the remote and local public keys are identical, poses a potential security risk for Bluetooth connections. It is crucial to update the Linux Kernel to the fixed version v4.19.192 to address this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially allow an attacker to perform a man-in-the-middle attack on Bluetooth connections.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will provide real-time alerts for open-source vulnerabilities.
Yes, the vulnerability has been fixed in Linux Kernel version v4.19.192. It is recommended to update your Kernel to the latest version to address the vulnerability.
There are no known exploits for this vulnerability at the moment. However, it is important to address the vulnerability to prevent potential security risks.
You can find more information about this vulnerability in the GSD-2021-1000524 JSON report available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000524.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
