Physical privilege escalation through undisclosed control-flow flaw
Published Jun 15, 2020 · Updated Aug 4, 2024
Insufficient control-flow management in Intel Innovation Engine Build and Signing Tool before 1.0.859 allows attackers to escalate privileges. Intel has not published the affected code path or the incorrect control-flow operation performed by the tool. Exploitation requires unauthenticated physical access, but Intel has not disclosed which privileges are gained or which firmware output is affected.
Summary
What happened
Insufficient control-flow management in Intel Innovation Engine Build and Signing Tool before 1.0.859 allows attackers to escalate privileges. Intel has not published the affected code path or the incorrect control-flow operation performed by the tool. Exploitation requires unauthenticated physical access, but Intel has not disclosed which privileges are gained or which firmware output is affected.
The record
- CVE
- CVE-2020-8675
- Published
- Jun 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Intel
- Product
- Intel Innovation Engine Build and Signing Tool
- Classifications
- Unavailable
- Attack vector
- physical
- 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before version 1.0.859
What conditions does exploitation require?
What is affected?
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
No sourced classifications are available.
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