dbcve.org
KillerApplication · Intel

CVE-2023-34983

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 input validation 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 input validation in Intel PROSet/Wireless and Intel Killer Wi-Fi software before version 22.240 allows an unauthenticated attacker within adjacent network range to potentially cause denial of service via malformed input processing.

MitigationUpdate Intel PROSet/Wireless or Intel Killer Wi-Fi software to version 22.240 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:< 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 Settings > Apps & Features (or use 'appwiz.cpl' in Run) and search for 'Intel PROSet/Wireless' or 'Intel Killer' in the installed programs list
    Affected if Either Intel PROSet/Wireless or Intel Killer Wi-Fi software appears in the installed programs
  2. Check Intel PROSet/Wireless version
    Right-click the Intel PROSet/Wireless icon in system tray or navigate to Control Panel > Programs > Programs and Features, locate Intel PROSet/Wireless and note the version shown in the Version column
    Affected if The version number displayed is lower than 22.240 (for example, 22.100, 21.x, etc.)
  3. Check Intel Killer Wi-Fi version
    Open Intel Killer Intelligence Center or Killer Performance Suite, look for the software version number typically displayed in the app's main window or about section
    Affected if The version number displayed is lower than 3.1423.712 (for example, 3.1xxx, 2.x, etc.)
  4. Verify Wi-Fi adapter is active
    Open Device Manager, expand 'Network adapters', look for Intel wireless adapter (such as Intel Wi-Fi 6 AX200/AX201/AX211) or Killer Wi-Fi adapter, right-click and select 'Enable device' if disabled; alternatively check if Wi-Fi is turned on in Windows Settings > Network & Internet > Wi-Fi
    Affected if Wi-Fi adapter is enabled and the wireless interface is active (the vulnerability requires the affected software to be actively processing network input)

You are affected if Intel PROSet/Wireless version is below 22.240 OR Intel Killer Wi-Fi version is below 3.1423.712, AND the wireless adapter is enabled and actively processing Wi-Fi connections.

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 the improper input validation vulnerability.

Recommended fix High confidence

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

  1. Identify the installed Intel PROSet/Wireless or Killer Wi-Fi software version on the system
  2. For Intel PROSet/Wireless: If version is lower than 22.240, download and install version 22.240 or later from the official Intel support website
  3. For Intel Killer Wi-Fi: If version is lower than 3.1423.712, download and install version 3.1423.712 or later from the official Intel or Killer support website
  4. Restart the system after installing the update to ensure the new drivers are properly loaded
  5. Verify the installed version matches or exceeds the fixed releases

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

Fix this in Killer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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