Code execution via arbitrary BIOS write
Published Feb 14, 2024 · Updated Nov 21, 2024
Arbitrary BIOS write in HP Z440, Z640, and Z840 Workstations before 2.62 allows local users with high privileges to execute code or halt service. HP identifies the flaw as an arbitrary write in system BIOS but does not disclose the affected routine, write target, or untrusted input path. Exploitation requires local access and high privileges; successful use can alter firmware-controlled execution or make the workstation unavailable.
Summary
What happened
Arbitrary BIOS write in HP Z440, Z640, and Z840 Workstations before 2.62 allows local users with high privileges to execute code or halt service. HP identifies the flaw as an arbitrary write in system BIOS but does not disclose the affected routine, write target, or untrusted input path. Exploitation requires local access and high privileges; successful use can alter firmware-controlled execution or make the workstation unavailable.
The record
- CVE
- CVE-2023-6138
- Published
- Feb 14, 2024
- Updated
- Nov 21, 2024
- Vendor
- Plantronics
- Product
- HP Workstation BIOS
- Classifications
- T1542.001, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 14, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 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 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