Bluetooth: SMP: Fail if remote and local public keys are identical
Summary
UVI-2021-1000527: Bluetooth: SMP: Fail if remote and local public keys are identical. Affects Kernel versions >= bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9, < 75523bbfb0eaead670c97fbcf096ca2ab556f0c0. 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 functionality 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 in the SMP protocol are identical, leading to potential security risks.
Vulnerability Detail
The vulnerability in the Bluetooth SMP protocol occurs when the remote and local public keys are the same. This can be exploited by an attacker to bypass the security measures and gain unauthorized access to the Bluetooth device. The impact of this vulnerability can vary depending on the context and the specific use case. However, it has the potential to compromise the confidentiality, integrity, and availability of the affected device. It is important to note that the actual impact and attack plausibility have not been proven yet.
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 →
Conclusion
The vulnerability in the Bluetooth SMP protocol, which affects the Kernel package in the Linux ecosystem, can potentially lead to unauthorized access and compromise the security of Bluetooth devices. It is crucial to update the Kernel to the fixed version (v4.4.270 or later) to mitigate the risk associated with this 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 can vary depending on the context and the specific use case. However, it has the potential to compromise the confidentiality, integrity, and availability of the affected device.
To mitigate the risk, it is recommended to update the Kernel to the fixed version (v4.4.270 or later) that addresses the vulnerability.
No specific workaround has been provided for this vulnerability. It is recommended to update the Kernel to the fixed version.
There is no information available regarding the exploitation of this vulnerability in the wild. However, it is always advisable to apply security patches and updates to protect against potential threats.
For more details about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
