Code execution via undisclosed firmware TOCTOU race
Published Jun 13, 2023 · Updated Jan 3, 2025
A TOCTOU race condition in HP PC BIOS allows physically proximate attackers to execute code, elevate privileges, interrupt service, or disclose data. HP has not disclosed the affected firmware locus or the check and later use whose intervening state change creates the race. Physical access is required; successful exploitation can cross the firmware trust boundary and compromise confidentiality, integrity, or system availability.
Summary
What happened
A TOCTOU race condition in HP PC BIOS allows physically proximate attackers to execute code, elevate privileges, interrupt service, or disclose data. HP has not disclosed the affected firmware locus or the check and later use whose intervening state change creates the race. Physical access is required; successful exploitation can cross the firmware trust boundary and compromise confidentiality, integrity, or system availability.
The record
- CVE
- CVE-2022-31637
- Published
- Jun 13, 2023
- Updated
- Jan 3, 2025
- Vendor
- Plantronics
- Product
- HP PC BIOS
- Classifications
- CWE-367
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 2023CVE publishedPublication date reported by the CVE source.
- Jan 3, 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