CVE-2024-53914
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 · uneditedAn issue was discovered in the server in Veritas Enterprise Vault before 15.2, ZDI-CAN-24344. 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 confidenceVeritas Enterprise Vault servers before version 15.2 contain an insecure deserialization vulnerability in their .NET Remoting TCP port implementation. Attackers can send specially crafted serialized .NET objects that, when deserialized without validation, allow arbitrary code execution on the affected server.
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< 15.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Enterprise Vault installation and versionLocate the Enterprise Vault installation directory and check the version information file, or use the enterprise vault administration console to view the installed version.Affected if The installed version is below 15.2 (e.g., 15.0, 14.x, earlier).
-
Identify .NET Remoting TCP service statusCheck if the Enterprise Vault services responsible for .NET Remoting are running. This typically includes services related to the store, directory, or administration components.Affected if The .NET Remoting services are running and accepting connections.
-
Check for open .NET Remoting TCP portsUse netstat or a port scanner to check if TCP ports 475, 485, or 495 are listening on the server. These are the typical ports used by Enterprise Vault's .NET Remoting implementation.Affected if Any of these ports (475, 485, 495) are open and listening on network interfaces accessible from untrusted networks.
-
Assess network exposure of remoting portsReview firewall rules or binding configurations to determine whether the .NET Remoting TCP ports are exposed to external or untrusted networks versus bound only to localhost or trusted internal subnets.Affected if The .NET Remoting TCP ports are bound to accessible network interfaces and can be reached by untrusted remote attackers.
A system is affected if it runs Enterprise Vault version below 15.2 with .NET Remoting TCP ports (475, 485, 495) exposed to untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped15.2
Upgrade to Enterprise Vault version 15.2 or later. If immediate patching is not possible, restrict network access to the .NET Remoting TCP port (typically TCP ports 475, 485, 495) using firewall rules to prevent untrusted remote connections.
Enterprise Vault 15.2
- Verify current Enterprise Vault version by checking the installed version in the Veritas Deployment and Configuration utility or via the VAC (Veritas Administration Console)
- Review Veritas Enterprise Vault 15.2 release notes and upgrade documentation at www.veritas.com for prerequisites and compatibility requirements
- Create a complete backup of the Enterprise Vault database and configuration
- Ensure all system prerequisites for version 15.2 are met, including OS compatibility and .NET framework requirements
- Stop all Enterprise Vault services before beginning the upgrade
- Run the Enterprise Vault 15.2 installer or use the Veritas Installation Wizard to perform the upgrade
- After upgrade completion, verify all Enterprise Vault services start successfully
- Confirm the upgraded version is 15.2 by checking the version information in the VAC or help-about section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-53914 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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