CVE-2016-0913
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 · uneditedThe client in EMC Replication Manager (RM) before 5.5.3.0_01-PatchHotfix, EMC Network Module for Microsoft 3.x, and EMC Networker Module for Microsoft 8.2.x before 8.2.3.6 allows remote RM servers to execute arbitrary commands by placing a crafted script in an SMB share.
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 confidenceEMC Replication Manager client and related modules allow remote RM servers to execute arbitrary commands by placing crafted scripts on SMB shares that the client subsequently executes without proper validation. This is a classic trust relationship exploitation where the client blindly executes scripts from what it considers a trusted 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<= 8.2.3.6= 3.0= 3.0.1<= 5.5.3CVSS 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.0/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.
-
Identify installed EMC Replication Manager versionCheck the installed version of EMC Replication Manager on the client system. This is typically visible in Add/Remove Programs, the program properties, or by running 'rmclient -version' if the command-line tool is available.Affected if The installed version is 5.5.3 or lower (any version <= 5.5.3).
-
Identify installed EMC Networker Module for Microsoft Applications versionCheck the installed version of EMC Networker Module for Microsoft Applications. This is typically visible in Add/Remove Programs, the program properties, or by checking the module's version through its management interface.Affected if The installed version is 3.0, 3.0.1, or any version <= 8.2.3.6.
-
Verify SMB share configuration for Replication ManagerExamine SMB shares configured for use with EMC Replication Manager. Check share permissions and determine whether remote RM servers have write access to these shares. Look for shares that the client uses for script storage or execution.Affected if Any SMB share used by the Replication Manager client is accessible to remote servers with write permissions, allowing untrusted servers to place executable scripts.
-
Check for script execution from remote sharesReview the Replication Manager client configuration to determine whether it is set to execute scripts or batch files from remote SMB shares. This may be visible in the client settings, configuration files, or management console.Affected if The client is configured to automatically execute scripts located on remote SMB shares without validation.
You are affected if either EMC Replication Manager <= 5.5.3 or EMC Networker Module for Microsoft Applications (versions 3.0, 3.0.1, or <= 8.2.3.6) is installed AND the client is configured to execute scripts from SMB shares accessible to remote servers.
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 patches (5.5.3.0_01-PatchHotfix for EMC RM, 8.2.3.6 for EMC Networker Module) and restrict SMB share access to prevent untrusted servers from placing executable content.
EMC Replication Manager 5.5.3.0_01-PatchHotfix or later; EMC Networker Module for Microsoft 8.2.3.6 or later; contact EMC for Network Module for Microsoft 3.x fixed release
- 1. Identify the current version of EMC Replication Manager or EMC Networker Module for Microsoft Applications installed in your environment.
- 2. For EMC Replication Manager: Upgrade to version 5.5.3.0_01-PatchHotfix or later.
- 3. For EMC Networker Module for Microsoft Applications 8.2.x: Upgrade to version 8.2.3.6 or later.
- 4. For EMC Network Module for Microsoft Applications 3.x: Contact EMC support to obtain the fixed release for version 3.x.
- 5. After upgrading, verify that the SMB share configuration restricts unauthorized script placement.
- 6. Test the upgraded functionality to ensure normal operations are maintained.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0913 — 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-2016-0913 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