Cyber Resilience

CVE-2023-0201

Memory Safety in Nvidia Bmc ≤ 1.08.00

Memory Safety
Published
22 April 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 6.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0020 11th percentile
Risk Priority 48 floored blend · peak EPSS

Summary

CVE-2023-0201 is a medium-severity Range Error (CWE-118) vulnerability in Nvidia Bmc. Its CVSS base score is 6.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

NVIDIA DGX-2 SBIOS contains a vulnerability in Bds, where a user with high privileges can cause a write beyond the bounds of an indexable resource, which may lead to code execution, denial of service, compromised integrity, and information disclosure.

CWE(s)
CWE-118CWE-787

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-0200Same product: Nvidia Bmc
CVE-2024-0110Same vendor: Nvidia
CVE-2023-0199Same vendor: Nvidia
CVE-2023-31031Same vendor: Nvidia
CVE-2023-31029Same vendor: Nvidia
CVE-2023-25528Same vendor: Nvidia
CVE-2023-31024Same vendor: Nvidia
CVE-2023-31030Same vendor: Nvidia
CVE-2023-25506Same vendor: Nvidia
CVE-2023-0182Same vendor: Nvidia

Affected Assets

nvidia
bmc
≤ 1.08.00

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SI-16 Memory Protection
addresses: CWE-787

Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce bounds checking and input validation that prevent range errors.

DE.CM-09 partial match
prevents

Runtime monitoring can detect adverse events triggered by out-of-bounds accesses but does not prevent them.

ID.RA-01 partial match
prevents

Vulnerability identification processes can surface range-error flaws after they exist but do not stop their introduction.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect range errors through fuzzing and boundary-value analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes input validation and bounds checking that can prevent range errors.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate bounds checking and safe indexing practices.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote defensive coding that limits out-of-bounds access.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require bounds checking and safe array access to prevent range errors.

A.8.32 Change management partial match
prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References