dbcve.org
KillerApplication · Intel

CVE-2024-28049

MEDIUM · 5.7 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 23.40.0 or later.
See remediation →
60/100
Remediation priority · Elevated
No privileges

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 in firmware for some Intel(R) PROSet/Wireless Software and Intel(R) Killer(TM) Wi-Fi wireless products before version 23.40 may allow an unauthenticated user to 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 · moderate confidence

Improper input validation in firmware for Intel PROSet/Wireless Software and Intel Killer Wi-Fi products before version 23.40 allows an unauthenticated attacker within adjacent network range to cause denial of service via specially crafted wireless frames.

MitigationUpdate Intel PROSet/Wireless Software or Intel Killer Wi-Fi firmware to version 23.40 or later to remediate the improper input validation vulnerability.

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

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
KillerApplication
Affected:< 23.40.0
Proset\/wireless WifiApplication
Affected:< 23.40.0

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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 hardware
    Check system device manager or use commands like 'lspci' (Linux) or 'Get-PnpDevice' (Windows) to list wireless network adapters. Look for Intel Killer or Intel PROSet/Wireless adapters.
    Affected if No Intel wireless adapter is present, then the system is not affected.
  2. Determine installed Intel wireless software version
    Open Intel PROSet/Wireless or Intel Killer software interface, or check via Windows Programs and Features, or use 'reg query' in Windows registry under HKLM\SOFTWARE\Intel for version information.
    Affected if The displayed version number is lower than 23.40.0.
  3. Check wireless adapter firmware version
    Access the wireless adapter properties in Device Manager (Windows) or use 'iw' or 'ethtool' commands (Linux) to retrieve the firmware version loaded on the wireless card.
    Affected if The firmware version is below 23.40.0.
  4. Verify wireless interface is active
    Check if the wireless adapter is enabled and connected or in monitor/managed mode. On Windows, use 'netsh wlan show interfaces'; on Linux, use 'ip link show' or 'iwconfig'.
    Affected if The wireless interface is active and capable of receiving frames, making it susceptible to specially crafted wireless frames from adjacent networks.

A system is affected if it has Intel Killer or Intel PROSet/Wireless WiFi hardware with software or firmware versions below 23.40.0 and the wireless interface is enabled and within adjacent network range of an attacker.

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
Upgrade available Upgrade to 23.40.0 or later
Fixed in 23.40.0
Interim mitigation

Update Intel PROSet/Wireless Software or Intel Killer Wi-Fi firmware to version 23.40 or later to remediate the improper input validation vulnerability.

Recommended fix High confidence

23.40.0 or later

  1. 1. Identify the installed Intel PROSet/Wireless Software or Killer Wi-Fi product version
  2. 2. Download the latest version from Intel's support website or use Intel's update utility
  3. 3. Install version 23.40.0 or later following Intel's standard installation procedures
  4. 4. Reboot the system to ensure the firmware update is applied
  5. 5. Verify the installed version is 23.40.0 or higher
Caveat Firmware updates may require system downtime and could reset wireless configuration settings

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

Fix this in Killer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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