SMM code execution via unvalidated destination pointer
Published Mar 11, 2022 · Updated Aug 3, 2024
Memory corruption in HP PC BIOS before 02.07.10 allows local users with kernel privileges to execute arbitrary code in SMM. A child software SMI handler accepts an unvalidated nested CommBuffer Dst pointer and passes it to CopyMemS, enabling writes into SMRAM. Exploitation requires ring 0 access and a crafted SMI request; successful code execution at ring -2 can modify protected firmware and persist across operating system reinstalls.
Summary
What happened
Memory corruption in HP PC BIOS before 02.07.10 allows local users with kernel privileges to execute arbitrary code in SMM. A child software SMI handler accepts an unvalidated nested CommBuffer Dst pointer and passes it to CopyMemS, enabling writes into SMRAM. Exploitation requires ring 0 access and a crafted SMI request; successful code execution at ring -2 can modify protected firmware and persist across operating system reinstalls.
The record
- CVE
- CVE-2022-23926
- Published
- Mar 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Plantronics
- Product
- HP PC BIOS
- Classifications
- T1542.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=before 02.07.10 (S05, S15 BIOS)
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
- BINARLY software-SMI exploitation procedureproof 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