Authentication bypass via spoofed HTTP header
Published Jul 18, 2023 · Updated Feb 13, 2025
Authentication bypass in AMI MegaRAC SP-X 12.0 through 12.3 allows remote authenticated users to gain unauthorized BMC access. The BMC HTTP authentication path trusts a client-supplied header as authorization evidence instead of validating the requester against the protected operation; AMI has not publicly identified the header or request handler. High-privileged network access is required, and exploitation can expose data, modify managed-system state, or interrupt service.
Summary
What happened
Authentication bypass in AMI MegaRAC SP-X 12.0 through 12.3 allows remote authenticated users to gain unauthorized BMC access. The BMC HTTP authentication path trusts a client-supplied header as authorization evidence instead of validating the requester against the protected operation; AMI has not publicly identified the header or request handler. High-privileged network access is required, and exploitation can expose data, modify managed-system state, or interrupt service.
The record
- CVE
- CVE-2023-34329
- Published
- Jul 18, 2023
- Updated
- Feb 13, 2025
- Vendor
- American Megatrends International
- Product
- MegaRAC SP-X
- Classifications
- CWE-306, CWE-290, CAPEC-21, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 18, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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.0 <12.4
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