SMM privilege escalation via unchecked buffer size
Published Jun 14, 2023 · Updated Dec 30, 2024
Out-of-bounds write in HP PC BIOS allows local users with DXE-phase code execution to elevate privileges into System Management Mode. The SMI handler validates nested Communication Buffer pointers against SMRAM but fails to enforce the supplied buffer size before sub_24E8 writes through them. Exploitation requires attacker-controlled code during the DXE boot phase and can corrupt SMRAM to execute arbitrary code with SMM privileges.
Summary
What happened
Out-of-bounds write in HP PC BIOS allows local users with DXE-phase code execution to elevate privileges into System Management Mode. The SMI handler validates nested Communication Buffer pointers against SMRAM but fails to enforce the supplied buffer size before sub_24E8 writes through them. Exploitation requires attacker-controlled code during the DXE boot phase and can corrupt SMRAM to execute arbitrary code with SMM privileges.
The record
- CVE
- CVE-2022-31644
- Published
- Jun 14, 2023
- Updated
- Dec 30, 2024
- Vendor
- Plantronics
- Product
- HP PC BIOS
- Classifications
- CWE-863, CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 14, 2023CVE publishedPublication date reported by the CVE source.
- Dec 30, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- BRLY-2022-011 technical proof of conceptproof of concept · demonstrated
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