dbcve.org
Enterprise VaultApplication · Veritas

CVE-2024-53911

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-24
Fix available
A fix is available. Upgrade to 15.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Veritas Enterprise Vault versions prior to 15.2 contain a deserialization vulnerability in the .NET Remoting TCP listener. Attackers can send malicious serialized .NET objects to this port, triggering unsafe deserialization that leads to arbitrary code execution without authentication.

MitigationUpgrade Veritas Enterprise Vault to version 15.2 or later. If immediate patching is not possible, block or restrict access to the .NET Remoting TCP port from untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise VaultApplication
Affected:< 15.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Enterprise Vault installation
    Check for the Enterprise Vault installation by examining common install paths (C:\Program Files\Veritas\Enterprise Vault) or query the Windows Services list for 'Enterprise Vault' services using 'Get-Service | Where-Object {$_.DisplayName -like "*Enterprise*Vault*"}'
    Affected if No Veritas Enterprise Vault installation is found - not affected. If found, continue to version check.
  2. Determine installed version
    Locate the EVVersion.exe or Enterprise Vault version information in the installation directory, or run 'Get-ItemProperty "HKLM:\SOFTWARE\Veritas\Enterprise Vault" -ErrorAction SilentlyContinue' to read the version from registry
    Affected if The installed version is 14.x or any version lower than 15.2 - potentially affected. If version is 15.2 or higher, not affected.
  3. Verify .NET Remoting service is enabled
    Check if the .NET Remoting service is running by examining Windows services for 'Enterprise Vault' processes listening on TCP ports. Use 'netstat -an | findstr LISTENING' to identify listening ports in the 1024-65535 range associated with Enterprise Vault processes
    Affected if The .NET Remoting TCP port is open and listening - vulnerable configuration present. If no such port is listening, not affected.
  4. Identify exposed .NET Remoting TCP port
    Run 'netstat -abno' to identify which process is bound to TCP ports and determine if Enterprise Vault components are bound to accessible network interfaces (0.0.0.0 or external IP rather than 127.0.0.1)
    Affected if The .NET Remoting TCP port is bound to all interfaces (0.0.0.0) or an external IP address - vulnerable to remote attack. If bound to 127.0.0.1 only, risk is reduced.

A system is affected if Veritas Enterprise Vault version is below 15.2 AND the .NET Remoting TCP service is running and exposed on a reachable network interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.2 or later
Fixed in 15.2
Interim mitigation

Upgrade Veritas Enterprise Vault to version 15.2 or later. If immediate patching is not possible, block or restrict access to the .NET Remoting TCP port from untrusted networks.

Recommended fix High confidence

Enterprise Vault 15.2

  1. 1. Review Veritas Enterprise Vault 15.2 upgrade documentation and release notes for prerequisites and compatibility requirements
  2. 2. Ensure you have a complete backup of your Enterprise Vault database and configuration
  3. 3. Schedule a maintenance window as upgrades may require downtime
  4. 4. Download Veritas Enterprise Vault 15.2 from Veritas Support portal
  5. 5. Run the upgrade installer on the Enterprise Vault server
  6. 6. Verify the upgrade was successful and all services are running
  7. 7. Monitor logs and system behavior post-upgrade to confirm stability
Caveat Review release notes for any configuration changes or feature modifications in 15.2 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Vault Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53911 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-53911 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data