Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LSummary
CVE-2024-48008 is a medium-severity ASP.NET Misconfiguration: Creating Debug Binary (CWE-11) vulnerability in Dell Recoverpoint For Virtual Machines. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 44th 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 CM-2 (Baseline Configuration) and CM-6 (Configuration Settings) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-43212
Vulnerability Data
Dell RecoverPoint for Virtual Machines 6.0.x contains a OS Command Injection vulnerability. An Low privileged remote attacker could potentially exploit this vulnerability leading to information disclosure ,allowing of unintended actions like reading files that may contain sensitive information
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V13.4.2V1.2.5V1.2.8V15.2.5
Mitigating Controls (NIST 800-53 r5) AI
Baseline configuration explicitly excludes debug binaries and enforces production settings that prevent exposure of debugging messages.
Requires the most restrictive configuration settings, directly stopping debug mode from being enabled in deployed ASP.NET binaries.
Developer testing and evaluation can discover missing or incorrect command sanitization during development.
Input validation directly neutralizes or rejects special characters that would otherwise alter OS command structure.
Least privilege reduces the permissions available to any process that could be subverted by injected commands.
Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.
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.
Configuration management directly prevents debug binaries from being deployed to production.
Secure SDLC practices include build and release configuration checks that eliminate debug binaries.
Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).
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 in development and acceptance can detect debug binaries but does not prevent their creation or deployment.
Configuration management directly requires disabling debug builds and removing diagnostic information from production releases.
Secure development life cycle mandates removal of debug symbols and verbose error handling before deployment.
Secure coding practices discourage leaving debug binaries in production but do not explicitly govern configuration settings.
Separation of environments reduces the chance that debug builds reach production but does not address the configuration weakness itself.