Local code execution via Legacy USB SMI callback
Published Jun 9, 2020 · Updated Sep 16, 2024
Arbitrary code execution in Lenovo BIOS on some Notebook and ThinkStation models allows local users to run code through a Legacy USB SMI callback. Lenovo identifies the vulnerable locus as the Legacy USB driver's SMI callback but does not disclose the incorrect operation or untrusted input. Exploitation requires local access, high privileges, and high complexity, and successful exploitation executes arbitrary code.
Summary
What happened
Arbitrary code execution in Lenovo BIOS on some Notebook and ThinkStation models allows local users to run code through a Legacy USB SMI callback. Lenovo identifies the vulnerable locus as the Legacy USB driver's SMI callback but does not disclose the incorrect operation or untrusted input. Exploitation requires local access, high privileges, and high complexity, and successful exploitation executes arbitrary code.
The record
- CVE
- CVE-2020-8322
- Published
- Jun 9, 2020
- Updated
- Sep 16, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 9, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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