CVE-2023-24023: Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow cer
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 70.2% of all records.
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: bpftool (AlmaLinux:8) 4.18.0-553.el8_10; kernel (AlmaLinux:8) 4.18.0-553.el8_10; kernel-abi-stablelists (AlmaLinux:8) 4.18.0-553.el8_10.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to bpftool (AlmaLinux:8) 4.18.0-553.el8_10; kernel (AlmaLinux:8) 4.18.0-553.el8_10; kernel-abi-stablelists (AlmaLinux:8) 4.18.0-553.el8_10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS.
- Published
- Nov 28, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 70th percentile
- CWE
- —
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| bluetooth | bluetooth core specification | cpe:2.3:a:bluetooth:bluetooth_core_specification |
| microsoft | windows 10 1809 | cpe:2.3:o:microsoft:windows_10_1809 |
| microsoft | windows 10 21h2 | cpe:2.3:o:microsoft:windows_10_21h2 |
| microsoft | windows 10 22h2 | cpe:2.3:o:microsoft:windows_10_22h2 |
| microsoft | windows 11 21h2 | cpe:2.3:o:microsoft:windows_11_21h2 |
| microsoft | windows 11 22h2 | cpe:2.3:o:microsoft:windows_11_22h2 |
| microsoft | windows 11 23h2 | cpe:2.3:o:microsoft:windows_11_23h2 |
| microsoft | windows server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
| microsoft | windows server 2022 | cpe:2.3:o:microsoft:windows_server_2022 |
| microsoft | windows server 2022 23h2 | cpe:2.3:o:microsoft:windows_server_2022_23h2 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft windows server 2019before 10.0.17763.5122
- microsoft windows server 2022before 10.0.20348.2113
- microsoft windows server 2022 23h2before 10.0.25398.531
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.el8_10 | 4.18.0-553.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.rt7.342.el8_10 | 4.18.0-553.rt7.342.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.rt7.342.el8_10 | 4.18.0-553.rt7.342.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.rt7.342.el8_10 | 4.18.0-553.rt7.342.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.rt7.342.el8_10 | 4.18.0-553.rt7.342.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.rt7.342.el8_10 | 4.18.0-553.rt7.342.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-kvm | before 4.18.0-553.rt7.342.el8_10 | 4.18.0-553.rt7.342.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.rt7.342.el8_10 | 4.18.0-553.rt7.342.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.rt7.342.el8_10 | 4.18.0-553.rt7.342.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.rt7.342.el8_10 | 4.18.0-553.rt7.342.el8_10 |
+96
Same product
bluetooth: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-25837Bluetooth® Pairing in Bluetooth Core Specification v1.0B through v5.3 may permit an unauthenticated MITM to acquire credentials with two pai30Monitor
- CVE-2022-25836Bluetooth® Low Energy Pairing in Bluetooth Core Specification v4.0 through v5.3 may permit an unauthenticated MITM to acquire credentials wi30Monitor
- CVE-2020-26556Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, able to conduct a successful brute-force attack on30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-31615Jun 25, 2021 · Unencrypted Bluetooth Low Energy baseband links in Bluetooth Core Specifications 4.0 through 5.2 may permit an adjacent device to inject a c21Monitor
- ← EarlierCVE-2020-35473Nov 8, 2022 · An information leakage vulnerability in the Bluetooth Low Energy advertisement scan response in Bluetooth Core Specifications 4.0 through 5.17Monitor
- ← EarlierCVE-2022-24695Jun 2, 2023 · Bluetooth Classic in Bluetooth Core Specification through 5.3 does not properly conceal device information for Bluetooth transceivers in Non17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:bpftool | 7.3.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.13.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.76-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-rt | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-debuginfo | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-devel | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-kvm | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules-extra | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo-common-x86_64 | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-devel | 0:4.18.0-553.rt7.342.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| rocky linux:kernel | 0:4.18.0-553.el8_10 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:kernel-rt | 0:4.18.0-553.rt7.342.el8_10 · Rocky Linux:8 | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150400.24.125.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-default | 5.3.18-150200.24.197.1 · SUSE:Linux Enterprise Live Patching 15 SP2 | Package registry (OSV) |
| suse:kernel-default-base | 5.3.18-150200.24.197.1.150200.9.101.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
+9
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0666 · Nov 29, 2023(Google Chrome Güvenlik Bildirimi)
- TR-23-0638 · Nov 15, 2023(Microsoft Güvenlik Güncellemesi)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.