Skip to main content
CVE-2024-53911VulnerabilityPublished Updated

CVE-2024-53911: 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

1. Immediately restrict network access to the .NET Remoting TCP port used by Veritas Enterprise Vault, ideally limiting it to trusted management networks or VPNs. 2. Implement network segmentation and firewall rules to block unauthorized inbound traffic to the vulnerable service. 3. Monitor network traffic for unusual activity or attempts to connect to the .NET Remoting port. 4. Apply the official security patch from Veritas as soon as it becomes available; prioritize patching in all affected environments. 5. If patching is delayed, consider disabling the .NET Remoting service or related features if feasible without disrupting business operations. 6. Conduct thorough audits of Enterprise Vault server logs and system behavior to detect any signs of compromise. 7. Employ endpoint detection and response (EDR) tools to identify suspicious process execution or code injection attempts. 8. Educate IT and security teams about the risks of insecure deserialization and ensure secure coding practices in custom integrations. 9. Regularly review and update incident response plans to include scenarios involving deserialization vulnerabilities and remote code execution. 10. Maintain up-to-date backups of critical data to enable recovery in case of compromise.

Description

An issue was discovered in the server in Veritas Enterprise Vault before 15.2, ZDI-CAN-24339. 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…