dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-24984

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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 input validation for some Intel(R) Wireless Bluetooth(R) products for Windows before version 23.40 may allow an unauthenticated user to potentially enable denial of service via adjacent 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

Improper input validation vulnerability in Intel Wireless Bluetooth drivers for Windows versions before 23.40 allows an unauthenticated attacker within Bluetooth adjacent range to potentially cause denial of service by sending specially crafted input that the driver fails to validate properly.

MitigationUpdate Intel Wireless Bluetooth drivers for Windows to version 23.40 or later to address the input validation flaw.

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

CVSS:3.1/AV:A/AC:L/PR:N/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. Locate Intel Wireless Bluetooth adapter in Device Manager
    Open Device Manager (devmgmt.msc), expand the 'Bluetooth' category, and identify the Intel Wireless Bluetooth adapter entry (typically named 'Intel(R) Wireless Bluetooth(R)' or similar).
    Affected if The adapter is present and uses an Intel driver.
  2. Check installed driver version
    Right-click the Intel Wireless Bluetooth adapter, select 'Properties', go to the 'Driver' tab, and note the 'Driver Version' displayed. Alternatively, run 'pnputil /enum-drivers /class Bluetooth' in an elevated Command Prompt to list installed Bluetooth driver packages and their versions.
    Affected if A driver version number is displayed that can be compared to the affected range.
  3. Compare version to affected range
    Compare the installed driver version number (e.g., 22.x.x, 23.x.x) against version 23.40. The first two numerical segments indicate the major version family. Ensure the full version string is read accurately as displayed in the Driver Version field.
    Affected if The installed version is lower than 23.40 (for example, 22.200.0.5, 23.30.0.4, or any version where the primary version number is 23 and the secondary number is below 40).

If the installed Intel Wireless Bluetooth driver version for Windows is below 23.40, the environment is affected by this vulnerability.

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.40 or later to address the input validation flaw.

Recommended fix High confidence

Intel Wireless Bluetooth driver version 23.40 or later for Windows

  1. Identify your specific Intel Wireless Bluetooth adapter model (via Device Manager > Bluetooth > Properties > Details > Hardware IDs)
  2. Visit Intel's support website (www.intel.com) and navigate to the drivers and software section for wireless products
  3. Search for your adapter model and download the Bluetooth driver version 23.40 or later for Windows
  4. Extract the downloaded driver package if necessary
  5. Run the installer (e.g., Setup.exe or IntelBluetoothSetup.exe) with administrator privileges
  6. Follow the on-screen prompts to complete the driver installation
  7. Restart your computer when prompted to ensure the new driver is fully initialized
  8. Verify the installed driver version via Device Manager to confirm version 23.40 or higher is now running

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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