Omission of Security-relevant Information Affecting bluez-libs-devel package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-RHEL8-BLUEZLIBSDEVEL-1338332
- published 26 Jul 2021
- disclosed 18 May 2020
How to fix?
There is no fixed version for RHEL:8 bluez-libs-devel.
NVD Description
Note: Versions mentioned in the description apply only to the upstream bluez-libs-devel package and not the bluez-libs-devel package as distributed by RHEL.
See How to fix? for RHEL:8 relevant fixed versions and status.
Pairing in Bluetooth® Core v5.2 and earlier may permit an unauthenticated attacker to acquire credentials with two pairing devices via adjacent access when the unauthenticated user initiates different pairing methods in each peer device and an end-user erroneously completes both pairing procedures with the MITM using the confirmation number of one peer as the passkey of the other. An adjacent, unauthenticated attacker could be able to initiate any Bluetooth operation on either attacked device exposed by the enabled Bluetooth profiles. This exposure may be limited when the user must authorize certain access explicitly, but so long as a user assumes that it is the intended remote device requesting permissions, device-local protections may be weakened.