dbcve.org
KillerApplication · Intel

CVE-2023-28720

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 3.1423.712 / 22.240 or later.
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 initialization for some Intel(R) PROSet/Wireless and Intel(R) Killer(TM) Wi-Fi software before version 22.240 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 · moderate confidence

Improper initialization vulnerability in Intel PROSet/Wireless and Intel Killer Wi-Fi software before version 22.240 allows an unauthenticated user with adjacent network access to potentially cause a denial of service condition.

MitigationUpdate Intel PROSet/Wireless or Intel Killer Wi-Fi software to version 22.240 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.

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:< 3.1423.712
Proset\/wirelessApplication
Affected:< 22.240

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. Check for Intel PROSet/Wireless installation
    Open Windows Settings > Apps & Features (or use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell) and look for entries containing 'Intel PROSet' or 'Intel Wireless'
    Affected if Intel PROSet/Wireless is listed with a version number below 22.240
  2. Check for Intel Killer Wi-Fi software installation
    Open Windows Settings > Apps & Features and look for entries containing 'Killer' or 'Intel Killer', or check C:\Program Files\Killer for the software directory
    Affected if Intel Killer software is installed with a version below 3.1423.712
  3. Verify installed version against affected ranges
    Compare the discovered version number to the affected ranges: Intel PROSet/Wireless < 22.240 or Intel Killer < 3.1423.712
    Affected if The installed version is lower than 22.240 for PROSet/Wireless or lower than 3.1423.712 for Killer Wi-Fi software
  4. Confirm Wi-Fi adapter is active
    Check Device Manager under Network adapters for Intel or Killer wireless adapters, or run 'netsh wlan show interfaces' to confirm an adapter is enabled and connected
    Affected if A vulnerable version of Intel wireless software is running with an active Wi-Fi adapter (the vulnerability requires adjacent network access to trigger)

A user is affected if Intel PROSet/Wireless version is below 22.240 or Intel Killer Wi-Fi software is below 3.1423.712, with the wireless adapter actively enabled on the system.

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 3.1423.712 / 22.240 or later
Fixed in 3.1423.71222.240
Interim mitigation

Update Intel PROSet/Wireless or Intel Killer Wi-Fi software to version 22.240 or later to remediate this vulnerability.

Recommended fix Moderate confidence

Intel PROSet/Wireless: version 22.240 or later | Killer Wi-Fi: version 3.1423.712 or later

  1. Identify the currently installed Intel PROSet/Wireless Wi-Fi software version via Windows Device Manager or the Intel PROSet control panel
  2. Identify the currently installed Killer Wi-Fi software version via Windows Device Manager or the Killer Control Center
  3. For Intel PROSet/Wireless: Download and install version 22.240 or later from the Intel website or your system OEM
  4. For Killer Wi-Fi: Download and install version 3.1423.712 or later from the Razer/Killer website or your system OEM
  5. Restart the computer after installation to ensure the Wi-Fi driver and software initialize correctly
  6. Verify the updated version is now installed
Caveat Ensure compatibility with your specific wireless adapter; OEM-specific versions may differ from Intel's direct downloads

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

Fix this in Killer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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