Adjacent service interruption via uncaught exception
Published Feb 14, 2024 · Updated Aug 14, 2024
An uncaught exception in Intel Wi-Fi software allows physically proximate attackers to interrupt service through adjacent wireless access. Intel identifies the weakness but does not disclose the affected code path, triggering input, or exception that escapes handling. Exploitation requires adjacent wireless access and no authentication; the documented consequence is limited to reduced availability.
Summary
What happened
An uncaught exception in Intel Wi-Fi software allows physically proximate attackers to interrupt service through adjacent wireless access. Intel identifies the weakness but does not disclose the affected code path, triggering input, or exception that escapes handling. Exploitation requires adjacent wireless access and no authentication; the documented consequence is limited to reduced availability.
The record
- CVE
- CVE-2023-26586
- Published
- Feb 14, 2024
- Updated
- Aug 14, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-248, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2024CVE publishedPublication date reported by the CVE source.
- Aug 14, 2024Record 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.
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