Local code execution via undisclosed UEFI flaw
Published Nov 21, 2022 · Updated Apr 29, 2025
Code injection in HP Workstation BIOS allows local users to execute arbitrary code through an unspecified UEFI firmware flaw. HP has not published the affected firmware locus or the operation that mishandles attacker-controlled input. Exploitation requires local access, and successful code execution can compromise confidentiality, integrity, and system availability.
Summary
What happened
Code injection in HP Workstation BIOS allows local users to execute arbitrary code through an unspecified UEFI firmware flaw. HP has not published the affected firmware locus or the operation that mishandles attacker-controlled input. Exploitation requires local access, and successful code execution can compromise confidentiality, integrity, and system availability.
The record
- CVE
- CVE-2021-3661
- Published
- Nov 21, 2022
- Updated
- Apr 29, 2025
- Vendor
- Plantronics
- Product
- HP Workstation BIOS
- Classifications
- CWE-94
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 2022CVE publishedPublication date reported by the CVE source.
- Apr 29, 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