CVE-2023-24023Public exploit

Traffic decryption and injection via forced key reuse

Published Nov 28, 2023 · Updated Aug 2, 2024

Session key derivation flaws in Bluetooth Core Specification 4.2 through 5.4 allow physically proximate attackers to decrypt BR/EDR traffic. During post-pairing encryption establishment, a spoofing man-in-the-middle can force both peers into legacy encryption and the Peripheral role, select the minimum key length, and fix every nonce that salts session-key generation. The attacker must remain within wireless range of two previously paired devices; a brute-forced reused key exposes recorded sessions and, below seven octets, enables live traffic injection.

CVSS severity6.8
Medium
EPSS probability1.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Session key derivation flaws in Bluetooth Core Specification 4.2 through 5.4 allow physically proximate attackers to decrypt BR/EDR traffic. During post-pairing encryption establishment, a spoofing man-in-the-middle can force both peers into legacy encryption and the Peripheral role, select the minimum key length, and fix every nonce that salts session-key generation. The attacker must remain within wireless range of two previously paired devices; a brute-forced reused key exposes recorded sessions and, below seven octets, enables live traffic injection.

The record

CVE
CVE-2023-24023
Published
Nov 28, 2023
Updated
Aug 2, 2024
Vendor
Bluetooth SIG, Inc.
Product
Bluetooth Core Specification
Classifications
CWE-326, CWE-300, T1557
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 28, 2023CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.2 <=5.4

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Bluetooth SIG, Inc. · Bluetooth Core Specificationversion=4.2 <=5.4

Published CVSS scores

6.8NIST NVDCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
6.4CISA-ADPCVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-326Inadequate Encryption Strength
CWE-300Channel Accessible by Non-Endpoint
T1557Adversary-in-the-Middle

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo