Local information disclosure via access control
Published Aug 18, 2022 · Updated May 5, 2025
Improper access control in Intel PROSet/Wireless WiFi and Killer WiFi products allows privileged users to disclose information locally. Intel identifies an access-control failure but does not publish the affected component or the specific operation that exposes data. Local access, high privileges, and user interaction are required; the documented consequence is information disclosure without integrity or availability impact.
Summary
What happened
Improper access control in Intel PROSet/Wireless WiFi and Killer WiFi products allows privileged users to disclose information locally. Intel identifies an access-control failure but does not publish the affected component or the specific operation that exposes data. Local access, high privileges, and user interaction are required; the documented consequence is information disclosure without integrity or availability impact.
The record
- CVE
- CVE-2022-21140
- Published
- Aug 18, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 18, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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.
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