LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25192: AMI MegaRAC SPX devices allow User Enumeration through Redfish.

AMI MegaRAC SPX devices allow User Enumeration through Redfish. The fixed versions are SPx12-update-7.00 and SPx13-update-5.00.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-25192 is a user enumeration flaw in AMI MegaRAC SPX Redfish interfaces. An unauthenticated network user may be able to determine valid accounts. This is not described as direct system takeover, but it can reduce attacker guesswork and support follow-on credential attacks against management interfaces.

Executive priority

Treat this as a moderate-priority management-plane issue. Prioritize externally reachable or broadly accessible BMC interfaces first, then schedule firmware updates through normal maintenance windows after confirming OEM applicability.

Technical view

The CVE describes user enumeration through Redfish on AMI MegaRAC SPX devices. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges or user interaction, with low confidentiality impact only. Fixed versions are SPx12-update-7.00 and SPx13-update-5.00.

Likely exposure

Exposure is most likely where AMI MegaRAC SPX BMC or management firmware is deployed and Redfish is reachable. The source bundle does not name specific OEM products or CPEs, so asset owners must confirm affected firmware through vendor or OEM inventories.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. The risk is still meaningful because unauthenticated, network-reachable management APIs can aid reconnaissance before password spraying, phishing, or other access attempts.

Researcher notes

The provided record lacks named affected OEM products, versions, and CPEs beyond AMI MegaRAC SPX and fixed SPx12/SPx13 releases. Avoid broad product claims without OEM confirmation. The stated impact is user enumeration with low confidentiality impact, mapped to CWE-668.

Mitigation direction

  • Upgrade to SPx12-update-7.00, SPx13-update-5.00, or later vendor-provided firmware.
  • Check OEM advisories for product-specific firmware packaging and deployment guidance.
  • Restrict BMC and Redfish access to dedicated management networks or VPNs.
  • Block internet exposure of Redfish management interfaces wherever possible.
  • Monitor management interfaces for unusual account discovery or authentication patterns.

Validation and detection

  • Inventory BMC firmware versions across servers and appliances.
  • Confirm whether each device runs AMI MegaRAC SPX firmware.
  • Compare deployed firmware against SPx12-update-7.00 and SPx13-update-5.00 fixes.
  • Verify Redfish interfaces are not reachable from untrusted networks.
  • Review management logs for suspicious unauthenticated or failed account-related 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 · low confidence lookup

CWE-668: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2023-25192 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-25192Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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-668 · source CWE mapping

Exposure of Resource to Wrong Sphere

Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.