SMM code execution via unchecked communication buffer
Published Mar 11, 2022 · Updated Aug 3, 2024
SMM memory corruption in HP PC BIOS before 02.07.10 on S05 and S15 BIOS families allows local users to execute arbitrary SMM code. A child SW SMI handler accepts a communication buffer without validating its size or location outside SMRAM, then CopyMem writes predictable data through an attacker-directed destination. Kernel-level privileges are required to trigger the software SMI; successful corruption permits S3-resume control-flow hijacking and persistent firmware code beneath the operating system.
Summary
What happened
SMM memory corruption in HP PC BIOS before 02.07.10 on S05 and S15 BIOS families allows local users to execute arbitrary SMM code. A child SW SMI handler accepts a communication buffer without validating its size or location outside SMRAM, then CopyMem writes predictable data through an attacker-directed destination. Kernel-level privileges are required to trigger the software SMI; successful corruption permits S3-resume control-flow hijacking and persistent firmware code beneath the operating system.
The record
- CVE
- CVE-2022-23934
- 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
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