Arbitrary code execution through undisclosed BIOS flaw
Published Jan 30, 2023 · Updated Mar 27, 2025
Code injection in HP PC BIOS on listed PC models allows local users to execute arbitrary code through an undisclosed firmware flaw. HP has not published the affected firmware locus or the operation that handles attacker-controlled input incorrectly. A local low-privileged account is required, and successful exploitation can elevate privileges, disclose information, or interrupt the system.
Summary
What happened
Code injection in HP PC BIOS on listed PC models allows local users to execute arbitrary code through an undisclosed firmware flaw. HP has not published the affected firmware locus or the operation that handles attacker-controlled input incorrectly. A local low-privileged account is required, and successful exploitation can elevate privileges, disclose information, or interrupt the system.
The record
- CVE
- CVE-2022-27537
- Published
- Jan 30, 2023
- Updated
- Mar 27, 2025
- Vendor
- Plantronics
- Product
- HP PC BIOS
- Classifications
- CWE-94, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 2023CVE publishedPublication date reported by the CVE source.
- Mar 27, 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