CVE-2024-0114
Raw vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-0114 is a high-severity Internal Asset Exposed to Unsafe Debug Access Level or State (CWE-1244) vulnerability in Custhelp (inferred from references). Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-0114 is a vulnerability in the HGX Management Controller (HMC) within NVIDIA Hopper HGX for 8-GPU systems. Published on 2025-03-05, it enables a malicious actor with administrative access on the Baseboard Management Controller (BMC) to gain administrator-level access to the HMC. The issue is classified under CWE-1244 and carries a CVSS v3.1 base score of 8.1 (AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H), indicating high severity due to its potential impact despite requiring high privileges.
Exploitation requires local access with administrative privileges on the BMC, low attack complexity, and no user interaction. A successful attack allows the actor to access the HMC as an administrator, potentially leading to arbitrary code execution, denial of service, further escalation of privileges, sensitive information disclosure, and data tampering within the affected HMC environment.
NVIDIA provides details on mitigation, including patches, in their security advisory at https://nvidia.custhelp.com/app/answers/detail/a_id/5561. Security practitioners should consult this bulletin for version-specific remediation steps.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-15915
Vulnerability Data
NVIDIA Hopper HGX for 8-GPU contains a vulnerability in the HGX Management Controller (HMC) that may allow a malicious actor with administrative access on the BMC to access the HMC as an administrator. A successful exploit of this vulnerability may…
more
lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations on logical access, directly stopping incorrect debug access levels from being granted to untrusted agents.
Requires least-privilege assignment of access rights, preventing over-privileged debug states on internal assets.
Mandates restrictive, approved configuration settings that would block unsafe debug access level assignments.
Requires application of security engineering principles such as least privilege and isolation during design of debug mechanisms.
Isolates security functions from non-security functions, reducing exposure of internal assets through debug paths.
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.
Defining and enforcing least-privilege access permissions directly prevents incorrect debug access levels from being assigned.
Configuration management practices ensure debug interfaces receive the intended access-level settings.
Secure development practices throughout the life cycle are the primary means of avoiding unsafe debug access assignments.
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.
Privileged access rights management can limit debug-level access but does not specifically address hardware debug interface misconfiguration.
Secure development lifecycle can include debug interface design reviews but does not guarantee correct access-level assignment.
A.8.27 mandates security-by-design, defense-in-depth, least privilege, assume-breach, and hardening plus explicit review against known attack patterns; this reaches the unsafe debug-access mis-assignment for some assets but leaves a bounded remainder (e.g. vendor-supplied debug logic, undocumented test modes, or silicon-level fuses outside the organization's engineering process).
Security testing can detect unsafe debug states, but testing alone does not prevent the design flaw.