CVE-2024-0801
Arcserve Udp 8.1 … 9.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-0801 is a high-severity Special Element Injection (CWE-75) vulnerability in Arcserve Udp. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — 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.
A denial of service vulnerability exists in Arcserve Unified Data Protection 9.2 and 8.1 within the ASNative.dll component. The flaw is tracked as CVE-2024-0801 with a CVSS 3.1 score of 7.5 and is associated with CWE-75, reflecting a remotely triggerable condition that can render the affected service unavailable while leaving confidentiality and integrity intact.
An unauthenticated attacker can exploit the issue over the network without user interaction to cause a denial of service, achieving high availability impact against exposed Arcserve Unified Data Protection installations.
The associated Tenable research note is available at https://www.tenable.com/security/research/tra-2024-07. The EPSS probability rose from lower values to a peak of 0.6314 on 2025-12-11 before receding to the current score of 0.4921, indicating a period of growing exploitation interest after public disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-16588
Vulnerability Data
A denial of service vulnerability exists in Arcserve Unified Data Protection 9.2 and 8.1 in ASNative.dll.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops special-element injection by rejecting or sanitizing untrusted data before it reaches a different control plane.
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 SDLC practices directly require input sanitization to block special-element injection.
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 catches injection vulnerabilities but does not itself implement the sanitization fix.
Logging can record injection attempts for detection but does not prevent the weakness.
Secure development life cycle mandates input validation and sanitization practices that directly prevent special-element injection.
Application security requirements explicitly call for controls against injection flaws including special-element handling.
Secure architecture principles reduce injection surfaces but do not prescribe the actual sanitization logic.
Secure coding standards require rigorous input sanitization, directly eliminating CWE-75.