dbcve.org
KillerApplication · Intel

CVE-2023-32644

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
Protection mechanism failure 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

A protection mechanism failure in Intel PROSet/Wireless and Intel Killer Wi-Fi software versions before 22.240 allows unauthenticated attackers within adjacent Wi-Fi range to potentially cause denial of service via adjacent network access.

MitigationUpgrade Intel PROSet/Wireless or Intel Killer Wi-Fi software to version 22.240 or later to address the protection mechanism failure.

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. Identify installed Intel Wi-Fi software
    Open Windows Control Panel > Programs and Features, or Settings > Apps & Features. Look for entries named 'Intel PROSet/Wireless' or 'Intel Killer Wi-Fi' or 'Killer Control Center' in the installed programs list.
    Affected if Neither Intel PROSet/Wireless nor Intel Killer Wi-Fi software is installed - the vulnerability does not apply.
  2. Check Intel PROSet/Wireless version
    If Intel PROSet/Wireless is listed, click on it to view the version, or right-click and select 'Change' or 'Uninstall' to reveal the version number. Alternatively, open Device Manager > Network Adapters > Intel Wi-Fi adapter > Properties > Driver tab to view the driver/software version.
    Affected if The displayed version is lower than 22.240.
  3. Check Intel Killer Wi-Fi version
    If Intel Killer software is listed, click on it to view the version number. Alternatively, open the Killer Control Center application if installed, then navigate to Settings or About section to find the software version.
    Affected if The displayed version is lower than 3.1423.712.
  4. Verify Wi-Fi adapter driver version as fallback
    Open Device Manager > Network Adapters. Right-click on Intel Wi-Fi adapter (such as Wi-Fi 6 AX200, AX201, etc.) > Properties > Driver tab. Note the driver version shown there.
    Affected if This step confirms the Intel Wi-Fi hardware is present, which is required for the affected software to run.

The environment is affected if Intel PROSet/Wireless version is below 22.240 or Intel Killer Wi-Fi version is below 3.1423.712, and the respective software is actively used.

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

Upgrade Intel PROSet/Wireless or Intel Killer Wi-Fi software to version 22.240 or later to address the protection mechanism failure.

Recommended fix High confidence

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

  1. Identify which Intel wireless product is installed: Intel(R) PROSet/Wireless or Intel(R) Killer(TM) Wi-Fi
  2. For Intel PROSet/Wireless: Upgrade to version 22.240 or later
  3. For Intel Killer Wi-Fi: Upgrade to version 3.1423.712 or later
  4. Verify the upgrade by checking the installed software version in Device Manager or the Intel PROSet/Wireless utility
  5. Restart the system after applying the update
Caveat Minor: Standard wireless driver updates may temporarily disconnect network; ensure backup connectivity before updating

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

Fix this in Killer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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