Cyber Resilience

CVE-2023-32651

Intel Killer ≤ 3.1423.712

Published
14 February 2024
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0036 29th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2023-32651 is a medium-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Intel Killer. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Improper validation of specified type of input 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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-26586Same product: Intel Killer
CVE-2023-28374Same product: Intel Killer
CVE-2023-25951Same product: Intel Killer
CVE-2023-34983Same product: Intel Killer
CVE-2023-32644Same product: Intel Killer
CVE-2023-32642Same product: Intel Killer
CVE-2023-28720Same product: Intel Killer
CVE-2023-33875Same product: Intel Killer
CVE-2024-28049Same product: Intel Killer
CVE-2024-23198Same product: Intel Killer

Affected Assets

intel
killer
≤ 3.1423.712
intel
proset\/wireless
≤ 22.240

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.1.1
  • V1.4.2
  • V2.1.1
  • V2.2.2

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input type validation during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect type-validation flaws but does not prevent them during development.

prevents

Secure development lifecycle mandates input validation and type checking to prevent improper type handling.

prevents

Application security requirements explicitly include validation of input data types and formats.

prevents

Secure architecture principles promote defensive input handling and type enforcement at system boundaries.

prevents

Secure coding standards directly require proper type validation of all external inputs.

References