dbcve.org
Enterprise VaultApplication · Veritas

CVE-2024-53909

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-24334. 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 deserializes untrusted data received on a .NET Remoting TCP port without proper validation. An unauthenticated remote attacker can send malicious serialized objects to this port to achieve arbitrary code execution on the affected server.

MitigationUpgrade to Veritas Enterprise Vault 15.2 or later. If immediate upgrade is not feasible, restrict network access to the .NET Remoting TCP port from untrusted sources.

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 is installed
    Check for the Enterprise Vault installation by looking for the service 'Enterprise Vault' in Windows Services, or check for the installation directory (typically C:\Program Files\Veritas\Enterprise Vault)
    Affected if The service or installation directory exists on the server
  2. Determine the installed version
    Open Windows Services, locate the Enterprise Vault service, right-click and select Properties to view the executable path. Navigate to that directory and check the file version of EnterpriseVault.exe, or use the command: dir "C:\Program Files\Veritas\Enterprise Vault\EnterpriseVault.exe"
    Affected if The version displayed is lower than 15.2 (for example, 15.0, 14.x, or earlier)
  3. Confirm .NET Remoting TCP port is enabled
    Examine the Enterprise Vault configuration files (typically stored in the installation directory or %ProgramData%\Veritas\Enterprise Vault) for .NET Remoting or TCP port settings, or check Windows Registry under HKLM\SOFTWARE\Veritas\Enterprise Vault for port configuration entries
    Affected if A .NET Remoting TCP listener or port is configured and active on the server
  4. Check network exposure of the remoting port
    Run netstat -an | findstr "LISTENING" to identify listening ports, then determine if the identified .NET Remoting TCP port is bound to 0.0.0.0 or an external interface rather than localhost/127.0.0.1
    Affected if The .NET Remoting TCP port is listening on all interfaces (0.0.0.0) or an external IP address and is accessible from untrusted network segments

The server is affected if Enterprise Vault version is below 15.2 AND the .NET Remoting TCP port is enabled and network-accessible from untrusted sources.

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 Veritas Enterprise Vault 15.2 or later. If immediate upgrade is not feasible, restrict network access to the .NET Remoting TCP port from untrusted sources.

Recommended fix High confidence

15.2

  1. 1. Identify the current version of Veritas Enterprise Vault installed in your environment
  2. 2. Schedule a maintenance window to perform the upgrade
  3. 3. Back up all Enterprise Vault databases and configuration settings
  4. 4. Download Enterprise Vault version 15.2 from the Veritas Support website (www.veritas.com)
  5. 5. Run the Enterprise Vault 15.2 installer on the server
  6. 6. Follow the upgrade wizard prompts, selecting the upgrade option
  7. 7. After upgrade completes, verify the version shows 15.2
  8. 8. Test critical Vault functions (archiving, retrieval, indexing) to ensure proper operation

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

Fix this in Enterprise Vault Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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