BMC compromise via undisclosed heap corruption
Published Jan 9, 2024 · Updated Jun 3, 2025
Heap-based buffer overflow in AMI MegaRAC SP-X 12 before 12.7 and 13 before 13.6 allows remote attackers to corrupt BMC memory. AMI identifies the BMC heap as the corruption locus but has not published the affected service, input field, or unsafe memory operation. Exploitation requires adjacent-network access, no authentication, and a high-complexity trigger; successful corruption can compromise BMC confidentiality and integrity or interrupt service.
Summary
What happened
Heap-based buffer overflow in AMI MegaRAC SP-X 12 before 12.7 and 13 before 13.6 allows remote attackers to corrupt BMC memory. AMI identifies the BMC heap as the corruption locus but has not published the affected service, input field, or unsafe memory operation. Exploitation requires adjacent-network access, no authentication, and a high-complexity trigger; successful corruption can compromise BMC confidentiality and integrity or interrupt service.
The record
- CVE
- CVE-2023-37297
- Published
- Jan 9, 2024
- Updated
- Jun 3, 2025
- Vendor
- American Megatrends International
- Product
- MegaRAC SP-X
- Classifications
- CWE-122, CWE-787
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 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?
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.
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