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: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-0801 is a high-severity Special Element Injection (CWE-75) vulnerability in Arcserve Udp. Its CVSS base score is 7.5 (High).
Operationally, 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
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 (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.
Logging can record injection attempts for detection but does not prevent the weakness.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reach special-element injection in the development phase, but leaves a bounded remainder (e.g. outsourced development without full assurance per 8.30, incomplete enforcement of guidelines across all languages/projects, or post-development injection vectors).
Application security requirements explicitly call for controls against injection flaws including special-element handling.
A.8.27 mandates security engineering principles including data validation/sanitization, distrust external input, security by design, and design reviews against attack patterns; this directly stops special-element injection from being exploitable in most cases, with a bounded remainder in incomplete implementation or novel attack patterns.
Secure coding standards require rigorous input sanitization, directly eliminating CWE-75.
Security testing catches injection vulnerabilities but does not itself implement the sanitization fix.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-75, a class-level weakness, and none of its children carries one either.