SMRAM corruption via unchecked communication buffer size
Published May 28, 2024 · Updated Aug 2, 2024
Improper buffer validation in Huawei CurieM-WFG9B BIOS 2.29 allows local users to corrupt SMRAM through a crafted communication buffer. The communication-buffer handler accepts a size that can make the buffer partially overlap data structures at the beginning of SMRAM. Local low-privilege OS access is required; Huawei reports OS service exceptions, while the CNA record identifies SMM code execution as a potential consequence.
Summary
What happened
Improper buffer validation in Huawei CurieM-WFG9B BIOS 2.29 allows local users to corrupt SMRAM through a crafted communication buffer. The communication-buffer handler accepts a size that can make the buffer partially overlap data structures at the beginning of SMRAM. Local low-privilege OS access is required; Huawei reports OS service exceptions, while the CNA record identifies SMM code execution as a potential consequence.
The record
- CVE
- CVE-2023-52710
- Published
- May 28, 2024
- Updated
- Aug 2, 2024
- Vendor
- MindSpore
- Product
- CurieM-WFG9B BIOS
- Classifications
- CWE-754, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=2.29
- Affected versionversion=OTA-CurieM-BIOS-2.29
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
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