CVE-2023-32642
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 · uneditedInsufficient adherence to expected conventions 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 · high confidenceInsufficient adherence to expected conventions in Intel(R) PROSet/Wireless and Intel(R) Killer(TM) Wi-Fi software before version 22.240 allows an unauthenticated attacker within adjacent wireless range to potentially cause denial of service via malformed or specially crafted wireless traffic.
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< 3.1423.712< 22.240CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Intel wireless softwareOpen Control Panel > Programs and Features (or Settings > Apps & Features on Windows 11) and look for 'Intel PROSet/Wireless' or 'Killer' software packages in the installed programs listAffected if Neither Intel PROSet/Wireless nor any Killer Wi-Fi software appears in installed programs
-
Check Intel PROSet/Wireless versionOpen Control Panel > Programs and Features, locate 'Intel PROSet/Wireless' or 'Intel PROSet', right-click and select 'Change' or 'Repair', or check the version in the software's About/Help sectionAffected if The displayed version number is less than 22.240 (for example, 22.110, 21.x series, etc.)
-
Check Intel Killer Wi-Fi software versionOpen Control Panel > Programs and Features, locate 'Killer' software (such as Killer Control Center, Killer Wireless, or Killer Performance Suite), check the version in the program properties or via the software's About sectionAffected if The displayed version number is less than 3.1423.712 (for example, 3.1245.500, 3.0.x series, etc.)
-
Verify wireless adapter driver version as secondary indicatorOpen Device Manager > Network adapters, right-click on Intel Wi-Fi adapter and select Properties > Driver tab, note the driver versionAffected if The driver version corresponds to software versions below 22.240 (driver dates prior to the 22.240 release)
You are affected if Intel PROSet/Wireless version is below 22.240 OR Intel Killer Wi-Fi software version is below 3.1423.712, and the affected software is running on your system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.1423.71222.240
Upgrade Intel PROSet/Wireless or Killer Wi-Fi software to version 22.240 or later to remediate the vulnerability.
Intel(R) PROSet/Wireless version 22.240 or later / Intel(R) Killer(TM) Wi-Fi version 3.1423.712 or later
- Identify the installed Intel PROSet/Wireless or Intel Killer Wi-Fi software version
- For Intel PROSet/Wireless: Upgrade to version 22.240 or later
- For Intel Killer Wi-Fi: Upgrade to version 3.1423.712 or later
- Verify the upgrade was successful by checking the software version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32642 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32642 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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