CVE-2023-0200
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 DGX-2 contains a vulnerability in OFBD where a user with high privileges and a pre-conditioned heap can cause an access beyond a buffers end, which may lead to code execution, escalation of privileges, denial of service, and 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 confidenceNVIDIA DGX-2 contains a heap-based buffer overflow vulnerability in the OFBD (OmniScale Fabric Bus Driver) where a high-privileged user with ability to pre-condition the heap can cause an out-of-bounds memory access beyond a buffer's end, potentially leading to code execution, privilege escalation, DoS, or information disclosure.
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< 1.08.00CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify the BMC firmware versionAccess the BMC web interface or use IPMI command 'ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> raw' or check via BMC web UI under Firmware/Inventory sectionAffected if The BMC firmware version is below 1.08.00 (e.g., 1.07.x, 1.06.x, etc.)
-
Confirm the system is a NVIDIA DGX-2 or compatible BMCCheck system model via 'ipmitool -I lanplus -H <bmc_ip> fru print' or BMC web interface System Information pageAffected if The system is a NVIDIA DGX-2 with an affected BMC firmware version less than 1.08.00
-
Verify OFBD driver is loaded or activeCheck BMC logs or driver status via 'ipmitool -I lanplus -H <bmc_ip> sel list' for OFBD-related messages, or check BMC web interface for driver/fabric bus driver statusAffected if OFBD (OmniScale Fabric Bus Driver) is loaded or running on the system with vulnerable BMC version
-
Check for heap corruption indicators in BMC event logsReview BMC System Event Log (SEL) for heap-related errors, memory corruption events, or unexpected driver failures using 'ipmitool -I lanplus -H <bmc_ip> sel elist'Affected if Event logs show heap corruption, out-of-bounds memory errors, or unexpected OFBD driver behavior on systems with BMC < 1.08.00
A user is affected if their NVIDIA DGX-2 system has a BMC firmware version below 1.08.00 and the OFBD driver is present and active.
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 data1.08.00
Apply NVIDIA's security patch for OFBD when available; restrict high-privileged access and monitor for unusual driver behavior until the fix is deployed.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0200 — 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-0200 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