CVE-2023-25192
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAMI MegaRAC SPX devices allow User Enumeration through Redfish. The fixed versions are SPx12-update-7.00 and SPx13-update-5.00.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAMI MegaRAC SPX devices contain a user enumeration vulnerability in the Redfish API. An unauthenticated remote attacker can send requests to the Redfish endpoint and differentiate between valid and invalid usernames based on varying HTTP response codes or timing differences, enabling username harvesting for subsequent attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12= 13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify MegaRAC SPX firmware versionAccess BMC web interface or use IPMI command 'ipmitool mc info' or 'ipmitool raw command' to retrieve firmware version informationAffected if Firmware version shows SPX 12 or SPX 13 (versions prior to SPx12-update-7.00 or SPx13-update-5.00)
-
Confirm Redfish API is network-accessibleAttempt HTTP GET request to /redfish/v1 endpoint on the BMC IP addressAffected if Redfish API responds to unauthenticated requests over the network
-
Test for user enumeration via HTTP response codesSend POST requests to Redfish session endpoint (/redfish/v1/SessionService/Sessions) with different username values and observe HTTP status codesAffected if Different status codes (e.g., 401 vs 404 vs 400) returned for valid versus invalid usernames
-
Test for user enumeration via timing differencesMeasure response time when authenticating with valid versus invalid usernames using repeated requestsAffected if Noticeable timing differences in responses between valid and invalid username attempts
User is affected if MegaRAC SPX firmware is version 12 or 13 and the Redfish API is network-accessible, with enumeration possible via differing HTTP responses or timing gaps between valid/invalid usernames.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate MegaRAC SPX firmware to versions SPx12-update-7.00 or SPx13-update-5.00 as provided by AMI. If immediate patching is not feasible, restrict network access to the Redfish management interface using firewalls or ACLs, and monitor for anomalous Redfish API access patterns.
SPx12-update-7.00 (for SPX v12) or SPx13-update-5.00 (for SPX v13)
- Identify the current MegaRAC SPX version (12 or 13) running on the device
- Obtain the corresponding firmware update package: SPx12-update-7.00 for version 12, or SPx13-update-5.00 for version 13
- Apply the firmware update through the device's standard update mechanism (Redfish UpdateService or web interface)
- After updating, verify the new firmware version is installed and the device is operational
- Confirm that the User Enumeration vulnerability through Redfish is no longer present by testing that user account responses are consistent (no different responses for valid vs invalid usernames)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25192 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data