Skip to main content
CVE-2024-53912VulnerabilityPublished Updated

CVE-2024-53912: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 15.2 : patch Veritas Enterprise Vault as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

AI-suggested

To mitigate CVE-2024-53912, organizations should prioritize upgrading Veritas Enterprise Vault to version 15.2 or later, where the vulnerability is addressed. If immediate patching is not feasible, network-level mitigations should be applied, such as restricting access to the .NET Remoting TCP port using firewalls or network segmentation to limit exposure to trusted hosts only. Employing intrusion detection/prevention systems (IDS/IPS) with signatures for suspicious deserialization attempts can help detect exploitation attempts. Additionally, monitoring logs for unusual activity on the TCP port and implementing strict access controls on the Enterprise Vault server can reduce risk. Organizations should also review and harden .NET Remoting configurations, disabling unnecessary remoting endpoints if possible. Regular backups and incident response plans should be updated to prepare for potential compromise. Coordination with Veritas support and staying informed on any released patches or advisories is essential for timely remediation.

Description

An issue was discovered in the server in Veritas Enterprise Vault before 15.2, ZDI-CAN-24341. It allows remote attackers to execute arbitrary code because untrusted data, received on a .NET Remoting TCP port, is deserialized.

References

Community reviews

Loading reviews…