Local privilege escalation via improper firmware initialization
Published Jun 15, 2020 · Updated Aug 4, 2024
Improper initialization in BIOS firmware for Intel 8th through 10th Generation Core processors allows local users to escalate privileges. Intel has not disclosed which BIOS component is left improperly initialized or how local input reaches the faulty state. Local access without prior privileges is required, and successful exploitation crosses a security boundary and can alter protected state or interrupt availability.
Summary
What happened
Improper initialization in BIOS firmware for Intel 8th through 10th Generation Core processors allows local users to escalate privileges. Intel has not disclosed which BIOS component is left improperly initialized or how local input reaches the faulty state. Local access without prior privileges is required, and successful exploitation crosses a security boundary and can alter protected state or interrupt availability.
The record
- CVE
- CVE-2020-0529
- Published
- Jun 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-665
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 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?
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