CVE-2021-44682
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 (6 of 6) was discovered in Veritas Enterprise Vault through 14.1.2. On start-up, the Enterprise Vault application starts several services that listen on random .NET Remoting TCP ports for possible commands from client applications. These TCP services can be exploited due to deserialization behavior that is inherent to the .NET Remoting service. A malicious attacker can exploit both TCP remoting services and local IPC services on the Enterprise Vault Server. This vulnerability is mitigated by properly configuring the servers and firewall as described in the vendor's security alert for this vulnerability (VTS21-003, ZDI-CAN-14079).
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 · moderate confidenceVeritas Enterprise Vault through 14.1.2 starts .NET Remoting TCP services on random ports that contain insecure deserialization vulnerabilities. A remote, unauthenticated attacker can send malicious serialized objects to these TCP remoting services or local IPC services to execute arbitrary code on the Enterprise Vault 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<= 14.1.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.
-
Confirm Enterprise Vault installationLocate the Enterprise Vault installation directory or check installed programs on the server for Veritas Enterprise VaultAffected if Enterprise Vault is installed on the system
-
Verify affected versionDetermine the installed Enterprise Vault version and confirm it is 14.1.2 or earlierAffected if The installed version is 14.1.2 or any version prior to 14.1.2
-
Identify running .NET Remoting TCP servicesUse netstat or similar network tools to enumerate TCP listening ports on the server, particularly on random/high ports that may indicate remoting servicesAffected if Unexpected TCP services are listening on random ports, especially if identified as .NET Remoting endpoints
-
Check for IPC servicesReview local services or processes that may expose .NET Remoting IPC channels accessible to local or remote attackersAffected if Enterprise Vault .NET Remoting IPC services are exposed and accessible
-
Assess network exposureReview firewall rules and network configuration to determine if the Enterprise Vault server is directly accessible from untrusted networks on the ports used by .NET Remoting servicesAffected if The server or .NET Remoting ports are accessible from untrusted networks or the internet without proper access controls
A user is affected if Enterprise Vault version 14.1.2 or earlier is installed and its .NET Remoting services are network-accessible to untrusted parties.
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 · scopedApply vendor-recommended server and firewall configurations from security alert VTS21-003 to restrict access to .NET Remoting services and limit exposure to trusted networks only.
14.2 or later (verify with Veritas for exact fixed release)
- Review Veritas security alert VTS21-003 for specific firewall and server configuration requirements to mitigate the .NET Remoting deserialization vulnerability
- Identify all running .NET Remoting TCP services on the Enterprise Vault server by examining the listening ports on startup
- Configure Windows Firewall to block unauthorized external access to the random TCP ports used by .NET Remoting services
- Restrict IPC access by implementing proper authentication and authorization on local IPC services
- Ensure Enterprise Vault servers are not directly exposed to untrusted networks
- Follow vendor-recommended network segmentation to isolate Enterprise Vault services
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44682 — 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-2021-44682 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