CVE-2024-53911

9.8 CRITICAL

📋 TL;DR

This vulnerability allows remote attackers to execute arbitrary code on Veritas Enterprise Vault servers by sending malicious data to a .NET Remoting TCP port. The issue affects all versions before 15.2 due to insecure deserialization of untrusted data. Organizations running vulnerable versions of Enterprise Vault are at risk of complete server compromise.

💻 Affected Systems

Products:
  • Veritas Enterprise Vault
Versions: All versions before 15.2
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability affects the .NET Remoting TCP port configuration which is typically enabled by default for Enterprise Vault server communications.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system takeover with administrative privileges, data exfiltration, ransomware deployment, and lateral movement across the network.

🟠

Likely Case

Remote code execution leading to data theft, service disruption, and installation of persistent backdoors.

🟢

If Mitigated

Limited impact if network segmentation prevents external access to the vulnerable port and proper authentication controls are in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability requires no authentication and exploits insecure deserialization, which is a well-understood attack vector with available exploitation frameworks.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 15.2 or later

Vendor Advisory: https://www.veritas.com/content/support/en_US/security/VTS24-014

Restart Required: Yes

Instructions:

1. Download Enterprise Vault version 15.2 or later from Veritas support portal. 2. Backup all Enterprise Vault data and configurations. 3. Run the installer with administrative privileges. 4. Follow the upgrade wizard. 5. Restart all Enterprise Vault services and verify functionality.

🔧 Temporary Workarounds

Block .NET Remoting TCP Port

windows

Restrict network access to the vulnerable .NET Remoting TCP port using firewall rules.

New-NetFirewallRule -DisplayName "Block Enterprise Vault Remoting" -Direction Inbound -LocalPort 8080 -Protocol TCP -Action Block

Disable .NET Remoting

windows

Configure Enterprise Vault to disable .NET Remoting if not required for functionality.

Modify Enterprise Vault configuration files to set remotingEnabled=false

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Enterprise Vault servers from untrusted networks
  • Deploy application control solutions to prevent execution of unauthorized binaries on affected systems

🔍 How to Verify

Check if Vulnerable:

Check Enterprise Vault version in the administration console or registry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Enterprise Vault\CurrentVersion

Check Version:

reg query "HKLM\SOFTWARE\Veritas\Enterprise Vault" /v CurrentVersion

Verify Fix Applied:

Verify version is 15.2 or higher in administration console and test .NET Remoting functionality remains operational if required.

📡 Detection & Monitoring

Log Indicators:

  • Unusual .NET Remoting connection attempts in Windows Event Logs
  • Failed deserialization errors in Enterprise Vault application logs
  • Unexpected process creation from Enterprise Vault services

Network Indicators:

  • Unusual traffic to Enterprise Vault .NET Remoting TCP port (typically 8080)
  • Malformed serialized data packets to Enterprise Vault servers

SIEM Query:

source="windows" AND (event_id=4688 OR event_id=4689) AND process_name="EnterpriseVault*" AND parent_process_name!="EnterpriseVault*"

🔗 References

📤 Share & Export