Unauthorized access via missed BIOS tamper trigger
Published Jun 9, 2020 · Updated Sep 17, 2024
An authentication bypass in Lenovo BIOS on listed ThinkPad models allows physically proximate attackers to gain unauthorized access via physical tampering. The BIOS tamper-detection mechanism fails to trigger when chassis tampering occurs, so intended firmware protection is not enforced. Physical access is required; the record describes unauthorized access with integrity and availability impact, and no remote attack path is described.
Summary
What happened
An authentication bypass in Lenovo BIOS on listed ThinkPad models allows physically proximate attackers to gain unauthorized access via physical tampering. The BIOS tamper-detection mechanism fails to trigger when chassis tampering occurs, so intended firmware protection is not enforced. Physical access is required; the record describes unauthorized access with integrity and availability impact, and no remote attack path is described.
The record
- CVE
- CVE-2020-8334
- Published
- Jun 9, 2020
- Updated
- Sep 17, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1542.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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
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