Denial of service via improper driver buffer restrictions
Published Apr 15, 2020 · Updated Aug 4, 2024
Buffer-restriction flaw in the Windows 10 kernel driver for Intel PROSet/Wireless WiFi before 21.70 allows attackers to interrupt service. Intel identifies improper buffer restrictions in the kernel-mode driver but does not disclose the driver file, input field, or exact buffer operation. The attack requires adjacent-network access and no prior privileges; the reported consequence is service interruption with no confidentiality or integrity impact.
Summary
What happened
Buffer-restriction flaw in the Windows 10 kernel driver for Intel PROSet/Wireless WiFi before 21.70 allows attackers to interrupt service. Intel identifies improper buffer restrictions in the kernel-mode driver but does not disclose the driver file, input field, or exact buffer operation. The attack requires adjacent-network access and no prior privileges; the reported consequence is service interruption with no confidentiality or integrity impact.
The record
- CVE
- CVE-2020-0558
- Published
- Apr 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel PROSet/Wireless WiFi Software
- Classifications
- T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Before version 21.70
What conditions does exploitation require?
What is affected?
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