dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2023-47859

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
Improper access control for some Intel(R) Wireless Bluetooth products for Windows before version 23.20 may allow an authenticated user to potentially enable denial of service via local access.

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 · high confidence

This is an improper access control vulnerability in Intel Wireless Bluetooth drivers for Windows. An authenticated local user could potentially cause a denial of service condition by exploiting insufficient access controls in the Bluetooth driver. The vulnerability exists in versions prior to 23.20.

MitigationUpdate Intel Wireless Bluetooth drivers for Windows to version 23.20 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Intel Wireless Bluetooth driver installation
    Open Device Manager, expand 'Bluetooth' section, look for Intel Bluetooth drivers (typically named 'Intel(R) Wireless Bluetooth(R)' or similar Intel Bluetooth adapter entries)
    Affected if No Intel Bluetooth driver is found in the system
  2. Check installed Intel Bluetooth driver version
    In Device Manager, right-click the Intel Bluetooth device, select 'Properties', go to 'Driver' tab, note the driver version number displayed
    Affected if Driver version exists but is lower than 23.20 (versions like 23.10.x, 22.x.x, 21.x.x, etc.)

The system is affected if an Intel Wireless Bluetooth driver for Windows is installed with a version number lower than 23.20.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel Wireless Bluetooth drivers for Windows to version 23.20 or later to remediate this vulnerability.

Recommended fix High confidence

Intel Wireless Bluetooth driver version 23.20 or later for Windows

  1. Identify the current Intel Wireless Bluetooth driver version via Device Manager (look under Bluetooth > Intel Wireless Bluetooth)
  2. Visit the Intel support website and download the latest Intel Wireless Bluetooth driver for your specific adapter model
  3. Ensure the downloaded driver version is 23.20 or later
  4. Run the installer and follow the on-screen prompts to update the driver
  5. Restart the computer if prompted to complete the installation
  6. Verify the new driver version is installed by checking Device Manager

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47859 — 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-47859 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