dbcve.org
Enterprise VaultApplication · Veritas

CVE-2024-53913

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-24343. 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 server before version 15.2 contains an insecure deserialization vulnerability in its .NET Remoting TCP port handling. Remote attackers can send malicious serialized data that gets deserialized without proper validation, leading to arbitrary code execution.

MitigationUpgrade to Enterprise Vault version 15.2 or later. If immediate upgrade is not feasible, restrict network access to the exposed .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. Confirm Enterprise Vault installation
    Check for Veritas Enterprise Vault installation by reviewing installed programs on the server, or look for Enterprise Vault-specific directories and services (such as 'Enterprise Vault' services in Windows Services).
    Affected if Veritas Enterprise Vault is installed on the server.
  2. Determine installed version
    Open the Enterprise Vault Administration Console and view the 'About' information, or check the installed version via the program's properties in Windows Add/Remove Programs.
    Affected if The installed version is any version prior to 15.2 (for example, 15.0, 14.x, 13.x, or earlier).
  3. Identify .NET Remoting TCP port configuration
    Review Enterprise Vault configuration files (such as EVEnterpriseVault.xml or similar configuration files in the Enterprise Vault installation directory) to locate the .NET Remoting TCP port settings, or use netstat to identify listening TCP ports associated with Enterprise Vault processes.
    Affected if The .NET Remoting TCP port is configured and listening.
  4. Check network exposure of the port
    Use network scanning tools or review firewall rules to determine whether the .NET Remoting TCP port is accessible from external network segments or untrusted networks.
    Affected if The .NET Remoting TCP port is reachable from network segments outside the trusted internal network.

A server is affected if it runs any version of Veritas Enterprise Vault prior to 15.2 with the .NET Remoting TCP port enabled and exposed to network attackers.

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 upgrade is not feasible, restrict network access to the exposed .NET Remoting TCP port using firewall rules or network segmentation.

Recommended fix High confidence

Enterprise Vault 15.2

  1. 1. Check current Enterprise Vault version by opening the Enterprise Vault Administration Console and navigating to the server properties, or by running 'evver.exe' from the command line
  2. 2. Create a complete backup of the Enterprise Vault database and export configuration settings
  3. 3. Download Veritas Enterprise Vault version 15.2 from the official Veritas Support website (www.veritas.com)
  4. 4. Review the Enterprise Vault 15.2 release notes and installation guide for any prerequisites
  5. 5. Run the Enterprise Vault 15.2 installer on the primary server, following the on-screen prompts
  6. 6. After installation, verify the upgrade was successful by checking the version number matches 15.2
  7. 7. Test critical vault services and ensure Enterprise Vault is functioning properly
  8. 8. Apply any subsequent security patches released after 15.2 if available
Caveat Security-focused upgrade; review release notes for any configuration changes or deprecated features

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 / QA6.0 h
42.0 hours of engineering $7,360
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,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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