Local BMC compromise via untrusted pointer dereference
Published Jan 9, 2024 · Updated Jun 17, 2025
Untrusted pointer dereference in AMI MegaRAC SP-X 12 through 12.7 and 13 before 13.6 allows local users to compromise the BMC. AMI identifies only the BMC as the locus and says it dereferences an attacker-controlled pointer, but publishes no affected interface, function, or input path. Low-privileged local access is required; successful exploitation can expose or alter BMC data and interrupt its operation.
Summary
What happened
Untrusted pointer dereference in AMI MegaRAC SP-X 12 through 12.7 and 13 before 13.6 allows local users to compromise the BMC. AMI identifies only the BMC as the locus and says it dereferences an attacker-controlled pointer, but publishes no affected interface, function, or input path. Low-privileged local access is required; successful exploitation can expose or alter BMC data and interrupt its operation.
The record
- CVE
- CVE-2023-34332
- Published
- Jan 9, 2024
- Updated
- Jun 17, 2025
- Vendor
- American Megatrends International
- Product
- MegaRAC SP-X
- Classifications
- CWE-822, CAPEC-129, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record 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=12 <=12.7
- Affected versionversion=13 <13.6
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