Local code execution via BIOS TOCTOU race
Published Jun 12, 2023 · Updated Jan 6, 2025
TOCTOU flaws in HP PC BIOS allow local users with low privileges to execute arbitrary code, interrupt service, or disclose data. HP has not published the affected BIOS code locus, the resource checked and later used, or the attacker-controlled change that wins the race. Exploitation requires local low-privilege access and high-complexity race timing; success can cross the firmware trust boundary and affect confidentiality, integrity, and availability.
Summary
What happened
TOCTOU flaws in HP PC BIOS allow local users with low privileges to execute arbitrary code, interrupt service, or disclose data. HP has not published the affected BIOS code locus, the resource checked and later used, or the attacker-controlled change that wins the race. Exploitation requires local low-privilege access and high-complexity race timing; success can cross the firmware trust boundary and affect confidentiality, integrity, and availability.
The record
- CVE
- CVE-2022-43777
- Published
- Jun 12, 2023
- Updated
- Jan 6, 2025
- Vendor
- Plantronics
- Product
- HP PC BIOS
- Classifications
- CWE-367, T1542.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 12, 2023CVE publishedPublication date reported by the CVE source.
- Jan 6, 2025Record 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=See HP Security Bulletin reference for affected versions.
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
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