LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25191: AMI MegaRAC SPX devices allow Password Disclosure through Redfish.

AMI MegaRAC SPX devices allow Password Disclosure through Redfish. The fixed versions are SPx_12-update-7.00 and SPx_13-update-5.00.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can expose passwords from AMI MegaRAC SPX baseboard management controllers through Redfish. Because Redfish is a remote management API, any reachable management interface could put server administration credentials at risk. The source names fixed SPx_12-update-7.00 and SPx_13-update-5.00 versions.

Executive priority

Treat this as a high-priority infrastructure hygiene issue for server management planes. Patch exposed or broadly reachable BMCs first, then validate network isolation and credential handling.

Technical view

CVE-2023-25191 is a CWE-522 password disclosure issue in AMI MegaRAC SPX Redfish functionality. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges, no user interaction, with high confidentiality impact only. The bundle does not provide affected CPEs or OEM-specific product mappings.

Likely exposure

Organizations using AMI MegaRAC SPX BMC firmware may be exposed, especially where Redfish or BMC management networks are reachable. Exact affected products are incomplete in the provided data.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk is still meaningful because the CVSS vector indicates unauthenticated remote access can disclose sensitive credentials.

Researcher notes

The public record is sparse: affected vendor/product fields are unavailable, and only fixed SPx branches are named. Avoid over-scoping without OEM correlation. Focus validation on firmware identification, Redfish exposure, and advisory mapping.

Mitigation direction

  • Upgrade to SPx_12-update-7.00, SPx_13-update-5.00, or later applicable vendor builds.
  • Check AMI and server OEM guidance for product-specific firmware packages.
  • Restrict Redfish and BMC access to dedicated management networks.
  • Block public internet access to management interfaces.
  • Rotate potentially exposed credentials after remediation if Redfish was reachable.

Validation and detection

  • Inventory servers using AMI MegaRAC SPX firmware.
  • Confirm installed firmware branch and update level.
  • Verify Redfish endpoints are not internet-exposed.
  • Review OEM advisories for exact model applicability.
  • Check BMC access logs for unexpected Redfish activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-522: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-25191 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-25191Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-522 · source CWE mapping

Insufficiently Protected Credentials

Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.