Unauthenticated account enumeration through Redfish
Published Feb 15, 2023 · Updated Mar 19, 2025
User enumeration in AMI MegaRAC SP-X 12 and 13 allows remote attackers to identify BMC accounts through unauthenticated Redfish requests. AMI has not published the Redfish endpoint, request field, or response difference that discloses whether an account exists. Network access to the BMC Redfish service is required; the documented consequence is account-name disclosure only.
Summary
What happened
User enumeration in AMI MegaRAC SP-X 12 and 13 allows remote attackers to identify BMC accounts through unauthenticated Redfish requests. AMI has not published the Redfish endpoint, request field, or response difference that discloses whether an account exists. Network access to the BMC Redfish service is required; the documented consequence is account-name disclosure only.
The record
- CVE
- CVE-2023-25192
- Published
- Feb 15, 2023
- Updated
- Mar 19, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 15, 2023CVE publishedPublication date reported by the CVE source.
- Mar 19, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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