Authenticated information disclosure via uninitialized firmware state
Published Nov 17, 2021 · Updated Aug 3, 2024
Improper initialization in Intel wireless firmware on Windows 10 allows remote authenticated users to disclose information via adjacent access. Intel has not published which firmware state is left uninitialized or how adjacent input exposes information. An authenticated user within wireless range is required; the published impact is limited to information disclosure.
Summary
What happened
Improper initialization in Intel wireless firmware on Windows 10 allows remote authenticated users to disclose information via adjacent access. Intel has not published which firmware state is left uninitialized or how adjacent input exposes information. An authenticated user within wireless range is required; the published impact is limited to information disclosure.
The record
- CVE
- CVE-2021-0053
- Published
- Nov 17, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-665
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 17, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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