CVE-2011-0647
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 irccd.exe service in EMC Replication Manager Client before 5.3 and NetWorker Module for Microsoft Applications 2.1.x and 2.2.x allows remote attackers to execute arbitrary commands via the RunProgram function to TCP port 6542.
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 confidenceThe irccd.exe service in EMC Replication Manager Client (versions before 5.3) and NetWorker Module for Microsoft Applications (2.1.x and 2.2.x) exposes the RunProgram function on TCP port 6542. This allows remote unauthenticated attackers to execute arbitrary commands on the affected system, providing complete remote code execution capability.
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<= 5.2.3= 2.0= 5.2= 5.2.2= 2.1= 2.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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 irccd.exe processCheck if the irccd.exe service process is running on the system using task manager or command-line process listing toolsAffected if The irccd.exe process is present and running - this is the vulnerable service component
-
Verify TCP port 6542 is listeningCheck if TCP port 6542 is open and listening on the system using netstat or port scanning tools (e.g., netstat -an | findstr 6542)Affected if Port 6542 is found to be in LISTENING state - this is the exposed attack surface
-
Check EMC Replication Manager Client versionInspect installed programs or check the application version through the EMC Replication Manager Client interface or Windows Add/Remove ProgramsAffected if Version is 5.2.3, 2.0, 5.2, or 5.2.2 - these versions are within the affected range
-
Check EMC Networker Module for Microsoft Applications versionInspect installed programs or check the application version through Windows Add/Remove Programs or the Networker Module documentationAffected if Version is 2.1 or 2.2 - these versions are within the affected range
-
Determine network exposure of port 6542Verify if TCP port 6542 is bound to all interfaces (0.0.0.0) rather than localhost only, or if the system is accessible from network segmentsAffected if Port 6542 is accessible from network hosts - remote unauthenticated attackers can reach the vulnerable service
A system is affected if it runs EMC Replication Manager Client <= 5.2.3 or Networker Module 2.1/2.2 with the irccd.exe service listening on TCP port 6542 and that port is network-accessible.
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 · scopedUpgrade EMC Replication Manager Client to version 5.3 or later. If immediate patching is not feasible, block inbound access to TCP port 6542 at the network perimeter using firewall rules or network segmentation to prevent unauthenticated external access.
EMC Replication Manager Client 5.3 or later
- Upgrade EMC Replication Manager Client to version 5.3 or later to remediate the vulnerability in irccd.exe service on TCP port 6542
- For Networker Module for Microsoft Applications versions 2.1.x and 2.2.x, contact EMC for the appropriate fixed version or patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.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 $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0647 — 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-2011-0647 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