Unauthorized access via failed BIOS tamper detection
Published Oct 9, 2023 · Updated Sep 19, 2024
Improper physical access control in Lenovo ThinkPad T14s Gen 3 and X13 Gen 3 BIOS before 1.30 allows attackers to gain unauthorized access. Under specific undisclosed circumstances, the BIOS tamper-detection mechanism fails to trigger, leaving the expected hardware-security response inactive. Physical proximity is required; Lenovo has not published the triggering circumstances or a more specific account of the resulting unauthorized access.
Summary
What happened
Improper physical access control in Lenovo ThinkPad T14s Gen 3 and X13 Gen 3 BIOS before 1.30 allows attackers to gain unauthorized access. Under specific undisclosed circumstances, the BIOS tamper-detection mechanism fails to trigger, leaving the expected hardware-security response inactive. Physical proximity is required; Lenovo has not published the triggering circumstances or a more specific account of the resulting unauthorized access.
The record
- CVE
- CVE-2022-3728
- Published
- Oct 9, 2023
- Updated
- Sep 19, 2024
- Vendor
- Lenovo
- Product
- ThinkPad T14s Gen 3 BIOS
- Classifications
- CWE-1263
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 9, 2023CVE publishedPublication date reported by the CVE source.
- Sep 19, 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 version<1.30 (R22ET60W)
What conditions does exploitation require?
What is affected?
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