dbcve.org
BmcOperating system · Nvidia

CVE-2023-25507

HIGH · 8.8 CVSS v3.1 Published 2023-04-22
Fix available
A fix is available. Upgrade to 3.39.30 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
NVIDIA DGX-1 BMC contains a vulnerability in the SPX REST API, where an attacker with the appropriate level of authorization can inject arbitrary shell commands, which may lead to code execution, denial of service, information disclosure, and data tampering.

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 confidence

The NVIDIA DGX-1 Baseboard Management Controller (BMC) contains a command injection vulnerability in the SPX REST API. An authenticated attacker with appropriate authorization can inject arbitrary shell commands through the API, leading to code execution with elevated privileges on the BMC firmware.

MitigationApply the NVIDIA-supplied firmware patch for DGX-1 BMC. Restrict access to the SPX REST API to only necessary, authorized personnel using network segmentation and principle of least privilege.

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
BmcOperating system
Affected:< 3.39.30

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the BMC device
    Confirm the target system is an NVIDIA DGX-1 Baseboard Management Controller by checking the hardware model or BMC system information through the BMC web interface or IPMI commands such as 'ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> mc info'
    Affected if The system is not an NVIDIA DGX-1 BMC, then this CVE does not apply
  2. Determine BMC firmware version
    Retrieve the BMC firmware version via the BMC web interface system information page, or use IPMI command 'ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> mc info' to obtain the firmware revision number
    Affected if The installed firmware version is lower than 3.39.30, indicating the system is potentially vulnerable
  3. Verify SPX REST API is enabled
    Check the BMC configuration settings through the web interface under API services or REST API settings, or query the BMC for available API endpoints using authenticated REST requests to identify if SPX REST API endpoints are accessible
    Affected if The SPX REST API is exposed and accessible, providing an attack surface for command injection
  4. Confirm API authentication status
    Review BMC user accounts and access control lists to determine which users have authorization to access the SPX REST API, or examine BMC audit logs for recent SPX REST API access attempts
    Affected if Any authenticated user with SPX REST API access exists, the command injection vector is present if the user has appropriate authorization

The environment is affected if the system is an NVIDIA DGX-1 BMC running firmware version lower than 3.39.30 with the SPX REST API enabled and accessible to authenticated users.

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
Upgrade available Upgrade to 3.39.30 or later
Fixed in 3.39.30
Interim mitigation

Apply the NVIDIA-supplied firmware patch for DGX-1 BMC. Restrict access to the SPX REST API to only necessary, authorized personnel using network segmentation and principle of least privilege.

Recommended fix High confidence

BMC version 3.39.30 or later

  1. Log into the NVIDIA DGX-1 system as an administrator with BMC access privileges
  2. Navigate to the NVIDIA DGX-1 BMC management interface (typically accessible via web UI or IPMI
  3. Locate the firmware update section in the BMC administration panel
  4. Download the BMC firmware version 3.39.30 or later from the official NVIDIA support portal at nvidia.custhelp.com
  5. Follow NVIDIA's documented firmware update procedure to apply the new BMC firmware
  6. Verify the BMC version after the update to confirm successful installation
  7. Restart the BMC services if required by the update procedure
  8. Test the SPX REST API functionality to ensure normal operations
Caveat BMC firmware updates carry risk of system inaccessibility if interrupted; ensure stable power and follow NVIDIA's update documentation precisely

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

Fix this in Bmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25507 — 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-25507 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