dbcve.org
Enterprise VaultApplication · Veritas

CVE-2024-53915

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-24405. 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 before version 15.2 contains a critical deserialization vulnerability in its .NET Remoting TCP port. Attackers can send malicious serialized objects to this port, causing arbitrary code execution without authentication.

MitigationUpgrade to Enterprise Vault version 15.2 or later. If immediate patching is not possible, restrict network access to the .NET Remoting TCP port via firewall rules or disable the service if not required.

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. Verify Enterprise Vault installation exists
    Check for the presence of the Veritas Enterprise Vault installation directory (typically C:\Program Files\Veritas\Enterprise Vault\) or look for the 'Enterprise Vault' service in Windows Services (services.msc).
    Affected if The product is not installed or the service does not exist.
  2. Determine installed version
    Open the Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Enterprise Vault\Install. Check the value of the 'Version' string entry, or examine the evadmin.exe or EnterpriseVault.exe file properties in the installation directory for version information.
    Affected if The installed version is below 15.2 (for example, 15.0, 15.1, or any version lower than 15.2).
  3. Identify .NET Remoting TCP port configuration
    Open the Enterprise Vault Administration Console or check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Enterprise Vault\Directory for entries containing 'TCP' or 'Remoting' port numbers. The default .NET Remoting port is typically 9090 or 9089.
    Affected if A .NET Remoting TCP port is configured and listening.
  4. Confirm the remoting port is listening
    Open Command Prompt and run 'netstat -ano | findstr :<port>' using the port identified in the previous step, or use PowerShell: 'Get-NetTCPConnection -LocalPort <port>' to verify the port is in a Listening state.
    Affected if The .NET Remoting TCP port is bound and listening on any interface.
  5. Assess network exposure of the remoting port
    Run 'netsh interface portproxy show all' or use a network scanner to determine which IP addresses the listening port is bound to (0.0.0.0 indicates full network exposure). Verify firewall rules allowing external access to this port.
    Affected if The port is accessible from network addresses other than localhost/127.0.0.1.

You are affected if Veritas Enterprise Vault is installed with a version below 15.2 AND the .NET Remoting TCP port is enabled and accessible from the network.

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 to Enterprise Vault version 15.2 or later. If immediate patching is not possible, restrict network access to the .NET Remoting TCP port via firewall rules or disable the service if not required.

Recommended fix High confidence

15.2

  1. 1. Identify the current version of Veritas Enterprise Vault by checking the installation or using the Veritas administration console
  2. 2. Create a full backup of the Enterprise Vault database and configuration
  3. 3. Review Veritas Enterprise Vault 15.2 release notes and upgrade documentation for any prerequisites
  4. 4. Download Veritas Enterprise Vault version 15.2 from the official Veritas support website
  5. 5. Schedule a maintenance window and ensure adequate downtime for the upgrade process
  6. 6. Apply the upgrade to Enterprise Vault following the standard upgrade procedure
  7. 7. Verify the upgrade was successful by checking the version number matches 15.2
  8. 8. Test critical vault functions and ensure normal operation
Caveat Review release notes for any configuration or feature changes between your current version and 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
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53915 — 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-53915 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