CVE-2023-31037
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 · uneditedNVIDIA Bluefield 2 and Bluefield 3 DPU BMC contains a vulnerability in ipmitool, where a root user may cause code injection by a network call. A successful exploit of this vulnerability may lead to code execution on the OS.
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 confidenceThis vulnerability exists in the ipmitool component running on NVIDIA Bluefield 2 and Bluefield 3 DPU BMC (Baseboard Management Controller). A root user on the BMC can achieve code injection through a network call, enabling arbitrary code execution on the underlying operating system. The attack vector is local (requiring root access on the BMC), but the impact is code execution with root privileges.
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= 2.8.2-46= 23.04= 23.07= 23.09CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm you are running an NVIDIA Bluefield 2 or Bluefield 3 DPUCheck the DPU model by querying the BMC or checking system documentation: `ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> raw` or check physical labels on the DPUAffected if The system is not a Bluefield 2 or Bluefield 3 DPU, then this CVE does not apply
-
Identify the BMC firmware versionRun: `ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> mc info` or access BMC web interface to view firmware versionAffected if The BMC firmware version matches 2.8.2-46, 23.04, 23.07, or 23.09
-
Verify ipmitool is accessible on the BMCTest connectivity to BMC ipmitool interface: `ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> -C 0 chassis status`Affected if ipmitool commands execute successfully against the BMC, indicating the tool is enabled and reachable
-
Confirm root-level BMC access existsAttempt to run a privileged ipmitool command requiring root: `ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> raw 0x00 0x08` or verify root credentials are availableAffected if Root credentials for BMC access are known or obtainable, enabling the local attack vector
You are affected if you have an NVIDIA Bluefield 2 or Bluefield 3 DPU with BMC firmware version 2.8.2-46, 23.04, 23.07, or 23.09 where ipmitool is accessible and root BMC access is possible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the NVIDIA Bluefield DPU BMC firmware to the version containing the security patch. If immediate patching is not possible, restrict network access to ipmitool functions and limit root-level BMC access to authorized personnel only.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31037 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-31037 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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