dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2023-31025

HIGH · 7.5 CVSS v3.1 Published 2024-01-12
Fix available
A fix is available. Upgrade to 00.22.05 or later.
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
NVIDIA DGX A100 BMC contains a vulnerability where an attacker may cause an LDAP user injection. A successful exploit of this vulnerability may lead to information disclosure.

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

The NVIDIA DGX A100 BMC contains an LDAP injection vulnerability that allows an attacker to manipulate LDAP user authentication queries through unsanitized input. Successful exploitation grants unauthorized access to LDAP directory information, potentially exposing sensitive user credentials and organizational directory data.

MitigationApply NVIDIA firmware updates for the DGX A100 BMC when available. Until then, restrict BMC network access to trusted management networks and implement strict input validation on any LDAP-integrated authentication 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
Dgx A100 FirmwareOperating system
Affected:< 00.22.05

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. Check DGX A100 BMC firmware version
    Access the BMC web interface or use IPMI command: `ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> fru print` or check via BMC web UI under 'System > Firmware' or 'About' section
    Affected if Firmware version is below 00.22.05 (e.g., 00.22.04, 00.21.x, etc.)
  2. Verify LDAP authentication is enabled
    Log into BMC web UI, navigate to 'Settings > Authentication' or 'User Management > LDAP' configuration page. Alternatively, check via IPMI: `ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> raw` command to query LDAP settings
    Affected if LDAP/LDAP authentication is configured and enabled on the BMC
  3. Confirm BMC network accessibility
    Check if the BMC management interface is exposed to untrusted networks. Use `nmap -p 443,623 <BMC_IP>` or verify network segment configuration
    Affected if BMC is accessible from untrusted or management networks without strict access controls

A system is affected if the DGX A100 BMC firmware version is below 00.22.05 AND LDAP authentication is enabled, allowing potential LDAP injection via unsanitized input fields in the LDAP configuration.

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 00.22.05 or later
Fixed in 00.22.05
Interim mitigation

Apply NVIDIA firmware updates for the DGX A100 BMC when available. Until then, restrict BMC network access to trusted management networks and implement strict input validation on any LDAP-integrated authentication interfaces.

Recommended fix Moderate confidence

DGX A100 BMC Firmware 00.22.05 or later

  1. Identify the current DGX A100 BMC firmware version using the BMC web interface or IPMI command (e.g., `ipmitool -I lanplus -H <bmc_ip> -U admin raw` or via the NVIDIA System Management interface)
  2. Download the DGX A100 firmware version 00.22.05 or later from the NVIDIA Enterprise Support portal (enterprise.nvidia.com) or NVIDIA NGC catalog
  3. Review the firmware update documentation specific to DGX A100 for proper update procedures
  4. Apply the firmware update to the BMC following NVIDIA's recommended process, which typically involves uploading the firmware via the BMC web interface or using NVIDIA's update tools
  5. After update completion, verify the BMC is running firmware version 00.22.05 or later and confirm LDAP configuration is not compromised
  6. Validate that LDAP authentication functions correctly post-update
Caveat Firmware updates to BMCs carry inherent risk; ensure proper backup of BMC configuration and follow NVIDIA's update checklist to avoid system downtime or BMC corruption

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

Fix this in Dgx A100 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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