dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2023-45866

MEDIUM · 6.3 CVSS v3.1 Published 2023-12-08
Fix available
A fix is available. Upgrade to 14.2 / 17.2 or later.
See remediation →
68/100
Remediation priority · Elevated
No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Bluetooth HID Hosts in BlueZ may permit an unauthenticated Peripheral role HID Device to initiate and establish an encrypted connection, and accept HID keyboard reports, potentially permitting injection of HID messages when no user interaction has occurred in the Central role to authorize such access. An example affected package is bluez 5.64-0ubuntu1 in Ubuntu 22.04LTS. NOTE: in some cases, a CVE-2020-0556 mitigation would have already addressed this Bluetooth HID Hosts issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-287

The mechanism that verifies who a user is can be side-stepped or fooled, letting an attacker act as someone they're not. Everything built on top of that identity then becomes untrustworthy. Fixing it means hardening the full authentication flow, including edge cases, tokens, and secondary paths.

General guidance for the improper authentication class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ubuntu LinuxOperating system
Affected:= 18.04= 20.04= 22.04= 23.10
FedoraOperating system
Affected:= 38= 39
Debian LinuxOperating system
Affected:= 10.0
AndroidOperating system
Affected:= 4.2.2= 6.0.1= 10.0= 11.0= 13.0= 14.0
Iphone OsOperating system
Affected:= 16.6< 17.2
macOSOperating system
Affected:= 12.6.7= 13.3.3>= 14.0, < 14.2
IpadosOperating system
Affected:< 17.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.2 / 17.2 or later
Fixed in 14.217.2
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to the latest bluez package available for your distribution (the fix commit 25a471a83e02e1effb15d5a488b3f0085eaeb675 is included in bluez versions after 5.64); For Apple devices: iOS/iPadOS 17.2+, macOS 14.2+

  1. For Ubuntu: Run 'sudo apt update && sudo apt upgrade bluez' to get the latest bluez package with the security fix
  2. For Fedora: Run 'sudo dnf update bluez' to install the patched version
  3. For Debian: Run 'sudo apt update && sudo apt upgrade bluez' to get the fixed package
  4. For Apple devices: Update to iOS 17.2 or later, iPadOS 17.2 or later, macOS 14.2 or later to receive the security patch
  5. For Android: Apply the latest Android security update from your device manufacturer

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45866 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45866 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data