Adjacent denial of service via undisclosed firmware validation
Published Nov 13, 2024 · Updated Jan 10, 2025
Improper input validation in Intel PROSet/Wireless and Intel Killer Wi-Fi firmware before 23.40 allows attackers to cause denial of service. Intel identifies the locus only as wireless firmware and has not disclosed the malformed input, parsing path, or failed validation operation. Exploitation requires adjacent wireless access and active user interaction, and the reported consequence is loss of availability rather than data disclosure or modification.
Summary
What happened
Improper input validation in Intel PROSet/Wireless and Intel Killer Wi-Fi firmware before 23.40 allows attackers to cause denial of service. Intel identifies the locus only as wireless firmware and has not disclosed the malformed input, parsing path, or failed validation operation. Exploitation requires adjacent wireless access and active user interaction, and the reported consequence is loss of availability rather than data disclosure or modification.
The record
- CVE
- CVE-2024-23198
- Published
- Nov 13, 2024
- Updated
- Jan 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 13, 2024CVE publishedPublication date reported by the CVE source.
- Jan 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo