CVE-2021-44678

9.8 CRITICAL

📋 TL;DR

This vulnerability in Veritas Enterprise Vault allows remote code execution through insecure .NET Remoting services that deserialize untrusted data. Attackers can exploit both TCP and local IPC services to execute arbitrary code on affected servers. All Enterprise Vault servers through version 14.1.2 are vulnerable unless properly configured.

💻 Affected Systems

Products:
  • Veritas Enterprise Vault
Versions: Through 14.1.2
Operating Systems: Windows Server
Default Config Vulnerable: ⚠️ Yes
Notes: Services start automatically on system boot, listening on random TCP ports for .NET Remoting.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise with administrative privileges, enabling data theft, ransomware deployment, or persistent backdoor installation.

🟠

Likely Case

Remote code execution leading to data exfiltration, lateral movement within the network, or service disruption.

🟢

If Mitigated

Limited to authenticated users or blocked by network segmentation, reducing attack surface significantly.

🌐 Internet-Facing: HIGH - Directly exploitable over network without authentication if services are exposed.
🏢 Internal Only: HIGH - Even internally, the vulnerability allows unauthenticated exploitation if network access exists.

🎯 Exploit Status

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

Exploitation leverages inherent .NET Remoting deserialization flaws, making reliable exploitation straightforward for attackers with network access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 14.1.2 with security updates or later versions

Vendor Advisory: https://www.veritas.com/content/support/en_US/security/VTS21-003

Restart Required: Yes

Instructions:

1. Download and install the security update from Veritas support portal. 2. Apply the update to all Enterprise Vault servers. 3. Restart the Enterprise Vault services. 4. Verify services are running correctly.

🔧 Temporary Workarounds

Network Segmentation and Firewall Rules

windows

Block all inbound traffic to Enterprise Vault servers except from authorized management systems and required clients.

# Windows Firewall example: New-NetFirewallRule -DisplayName "Block EV Remoting" -Direction Inbound -Protocol TCP -LocalPort Any -Action Block

Disable .NET Remoting Services

windows

Configure Enterprise Vault to disable vulnerable .NET Remoting services as described in vendor advisory.

# Modify Enterprise Vault configuration files per VTS21-003 instructions

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Enterprise Vault servers from untrusted networks.
  • Apply vendor-recommended configuration changes to disable vulnerable services and use firewall rules to block all unnecessary ports.

🔍 How to Verify

Check if Vulnerable:

Check Enterprise Vault version via Administration Console or registry: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Enterprise Vault\CurrentVersion

Check Version:

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

Verify Fix Applied:

Verify version is 14.1.2 with security updates applied and check that .NET Remoting services are disabled per vendor guidance.

📡 Detection & Monitoring

Log Indicators:

  • Unusual process creation from Enterprise Vault services
  • Failed authentication attempts to Enterprise Vault remoting ports
  • Unexpected network connections to high-numbered TCP ports

Network Indicators:

  • Traffic to random high TCP ports (1024-65535) from untrusted sources
  • .NET Remoting protocol traffic to Enterprise Vault servers

SIEM Query:

source="EnterpriseVault" AND (event_id=4688 OR event_id=5156) AND process_name CONTAINS "powershell" OR "cmd"

🔗 References

📤 Share & Export