CVE-2025-23302
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:LSummary
CVE-2025-23302 is a medium-severity Internal Asset Exposed to Unsafe Debug Access Level or State (CWE-1244) vulnerability in Custhelp (inferred from references). Its CVSS base score is 4.2 (Medium).
Operationally, ranked at the 2th 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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-26737
Vulnerability Data
NVIDIA HGX and DGX contain a vulnerability where a misconfiguration of the LS10 could enable an attacker to set an unsafe debug access level. A successful exploit of this vulnerability might lead to denial of service.
- CWE(s)
Related Threats
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.
Secure development practices throughout the life cycle are the primary means of avoiding unsafe debug access assignments.
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.
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.
Security testing can detect unsafe debug states, but testing alone does not prevent the design flaw.
Privileged utility programs may include debug tools, but the control does not address hardware debug access levels.
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.
Secure system architecture principles can require proper debug port isolation, yet the control is broader than this specific weakness.
Information access restriction can reduce exposure of internal assets but does not cover physical debug port access levels.