dbcve.org
Enterprise VaultApplication · Veritas

CVE-2024-53910

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-24336. 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 before 15.2 contain a deserialization vulnerability in their .NET Remoting TCP port implementation. Attackers can send malicious serialized .NET objects to this port, causing arbitrary code execution without authentication.

MitigationUpgrade Veritas Enterprise Vault to version 15.2 or later. If immediate patching is not possible, restrict network access to the .NET Remoting TCP port using firewall rules or network segmentation.

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. Identify the installed Enterprise Vault version
    Use the Veritas Enterprise Vault administration console, check the program's 'About' information, or query the Vault Server program properties to find the exact version number
    Affected if The version is below 15.2 (for example, 15.0, 14.x, or earlier)
  2. Locate the .NET Remoting TCP port
    Check the Enterprise Vault configuration files (typically in the installation directory) or use netstat -an to identify ports with TCP listeners associated with the Enterprise Vault process
    Affected if A TCP port is bound and listening for .NET Remoting connections
  3. Determine if the .NET Remoting TCP port is network-accessible
    Run a port scan from an external system (for example, nmap -p <port> <target>) or check firewall rules to see if the port accepts remote connections
    Affected if The port accepts connections from untrusted networks or is exposed externally
  4. Verify the Enterprise Vault service is running
    Check Windows Services console or run sc query EnterpriseVault or Get-Service EnterpriseVault to confirm the service status
    Affected if The Vault service is running with the vulnerable .NET Remoting endpoint active

You are affected if Enterprise Vault version is below 15.2 AND the .NET Remoting TCP port is open and accessible on your 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 Veritas Enterprise Vault to version 15.2 or later. If immediate patching is not possible, restrict network access to the .NET Remoting TCP port using firewall rules or network segmentation.

Recommended fix High confidence

Enterprise Vault 15.2

  1. 1. Inventory all Enterprise Vault servers in the environment that are running versions prior to 15.2
  2. 2. Schedule a maintenance window for the upgrade (this is a critical security update)
  3. 3. Back up the Enterprise Vault configuration and database before proceeding
  4. 4. Download Enterprise Vault version 15.2 from the Veritas Support website (support.veritas.com)
  5. 5. Run the Enterprise Vault 15.2 installer on each affected server, following Veritas upgrade documentation
  6. 6. Verify the upgrade was successful by checking the Enterprise Vault version and that services started properly
  7. 7. Confirm the .NET Remoting TCP port is no longer accepting untrusted deserialized data
Caveat Standard upgrade - review Veritas release notes for version 15.2 for any configuration or compatibility changes before proceeding

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

Fix this in Enterprise Vault Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,200
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,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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