CVE-2024-53910: Veritas Enterprise Vault · Deserialization of Untrusted Data
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in 15.2 : patch Veritas Enterprise Vault as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- Veritas Enterprise Vault before 15.2
- Patch
- Available – fixed in 15.2
CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-53910, organizations should take the following specific actions: 1) Immediately restrict network access to the .NET Remoting TCP port used by Veritas Enterprise Vault servers by implementing firewall rules or network segmentation to limit exposure to trusted management networks only. 2) Monitor network traffic and server logs for unusual or unexpected connections on the vulnerable port, looking for signs of exploitation attempts or anomalous deserialization activity. 4) If patching is not immediately possible, consider disabling or blocking the .NET Remoting service if it is not essential for operations, or apply application-level controls to validate and sanitize incoming serialized data. 5) Conduct a thorough review of existing security controls around Enterprise Vault servers, including endpoint protection, intrusion detection systems, and network segmentation, to reduce the attack surface. 6) Educate IT and security teams about the risks of deserialization vulnerabilities and ensure incident response plans include scenarios involving remote code execution on critical archiving infrastructure. 7) Maintain up-to-date backups of Enterprise Vault data and configurations to enable recovery in case of compromise. These measures, combined with vigilant monitoring, will help reduce the risk until official patches are deployed.
Description
An issue was discovered in the server in Veritas Enterprise Vault before 15.2, ZDI-CAN-24336. It allows remote attackers to execute arbitrary code because untrusted data, received on a .NET Remoting TCP port, is deserialized.