dbcve.org
Megarac Sp XOperating system · Ami

CVE-2023-25191

HIGH · 7.5 CVSS v3.1 Published 2023-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
AMI MegaRAC SPX devices allow Password Disclosure through Redfish. The fixed versions are SPx_12-update-7.00 and SPx_13-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 · moderate confidence

AMI MegaRAC SPX baseboard management controller (BMC) devices contain a password disclosure vulnerability in the Redfish API implementation. An attacker with network access to the BMC could exploit this to obtain sensitive credentials used for device authentication.

MitigationApply the available firmware updates: SPx_12-update-7.00 for SPx_12 version line or SPx_13-update-5.00 for SPx_13 version line. Restrict Redfish API access to trusted networks or management interfaces.

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
Megarac Sp XOperating system
Affected:= 12= 13

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify BMC firmware version
    Access the BMC web interface or use IPMI/Redfish command to retrieve the firmware version. Common methods: 'ipmitool -I lanplus -H <BMC_IP> -U <user> mc info' or via Redfish GET /redfish/v1/Managers/Self
    Affected if Version displays as 12.x or 13.x (any minor version)
  2. Confirm Redfish API is enabled
    Verify the Redfish service is running on the BMC by attempting to access the Redfish endpoint: GET https://<BMC_IP>/redfish/v1/ or checking BMC service status via IPMI
    Affected if Redfish API responds with a valid JSON service root document
  3. Check Redfish API network exposure
    Determine if the BMC Redfish port (typically 443 or 80) is accessible from untrusted networks. Use network scanning or review firewall/ACL rules: 'nmap -p 443,80 <BMC_IP>' or review BMC network settings
    Affected if Redfish port is open to networks outside trusted management interfaces
  4. Inspect Redfish Manager account resource
    Query the Redfish Manager account service endpoint: GET /redfish/v1/Managers/Self/Accounts to enumerate user accounts. Note: This may require authentication, but the vulnerability allows credential disclosure
    Affected if Endpoint is accessible and returns account information without proper hardening

You are affected if your BMC runs firmware version 12.x or 13.x AND the Redfish API is network-accessible, as the password disclosure occurs through Redfish endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the available firmware updates: SPx_12-update-7.00 for SPx_12 version line or SPx_13-update-5.00 for SPx_13 version line. Restrict Redfish API access to trusted networks or management interfaces.

Recommended fix High confidence

SPx_12-update-7.00 (for version 12) or SPx_13-update-5.00 (for version 13)

  1. Identify the current MegaRAC SPX version (12 or 13) by accessing the device Redfish interface or BMC web UI
  2. Download the appropriate firmware update: SPx_12-update-7.00 for version 12 or SPx_13-update-5.00 for version 13
  3. Apply the firmware update through the Redfish UpdateService or BMC firmware update interface
  4. Verify the update was successful by checking the firmware version after reboot
  5. Confirm the password disclosure vulnerability is resolved by verifying credentials are no longer exposed through Redfish responses

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Megarac Sp X Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25191 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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