Privileged local denial of service
Published Jun 9, 2021 · Updated Aug 3, 2024
Improper initialization in firmware for some Intel Processors allows local users to cause a denial of service through local access. Intel has not disclosed the affected firmware routine, the state left uninitialized, or the operation that later consumes that state. Exploitation requires high privileges on the host; the resulting service interruption is documented, but Intel does not specify whether it is a hang, crash, or reboot.
Summary
What happened
Improper initialization in firmware for some Intel Processors allows local users to cause a denial of service through local access. Intel has not disclosed the affected firmware routine, the state left uninitialized, or the operation that later consumes that state. Exploitation requires high privileges on the host; the resulting service interruption is documented, but Intel does not specify whether it is a hang, crash, or reboot.
The record
- CVE
- CVE-2021-0095
- Published
- Jun 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-665, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 9, 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.
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