CVE-2023-45866
Description
A flaw was found in the HID Profile in BlueZ that opens doors for unauthorized connections, especially by devices like keyboards, to inject keystrokes without user confirmation. BlueZ lacks proper restrictions on non-bonded devices, creating a risk for attackers that are physically close to inject keystrokes and execute arbitrary commands when the device is in a discoverable state.
Statement
BlueZ was found to inadequately limit non-bonded devices from injecting HID events into the input subsystem. This vulnerability could permit a nearby attacker (physically proximate) to inject keystrokes and carry out arbitrary commands when the device is in discoverable mode.
Mitigation
Put Bluetooth device in non-discoverable mode / disable incoming pairing.
Or
Disable Bluetooth. Instructions on disabling bluetooth in Red Hat Enterprise Linux are available at: https://access.redhat.com/solutions/2682931
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.3 | 6.3 | N/A |
| Attack Vector | Adjacent Network | Adjacent Network | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | None | None | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | Low | Low | N/A |
| Integrity Impact | Low | Low | N/A |
| Availability Impact | Low | Low | N/A |
Vector
Red Hat: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Red Hat CVSS v3 Score Explanation
Successfully exploiting bluez results in some confidentiality loss, but the attacker can't control what information is accessed, limiting the impact. This disclosure doesn't cause a direct, serious loss to the affected component, so confidentiality impact is low.
After exploiting bluez, data modification is possible, but the attacker lacks control over the consequences or extent, resulting in a low integrity impact as the modification doesn't directly and severely affect the component.
While resource availability experiences reduced performance, repeated exploitation doesn't allow the attacker to completely deny service to legitimate users. The impacted component's resources are either partially available consistently or fully available intermittently, resulting in a low availability impact overall.
Understanding the Weakness (CWE)
Confidentiality,Integrity,Availability,Access Control
Technical Impact: Modify Memory; Read Memory; Execute Unauthorized Code or Commands; Gain Privileges or Assume Identity; Bypass Protection Mechanism; Other
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
