CVE-2009-1120
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 · uneditedEMC RepliStor Server Service before ESA-09-003 has a DoASOCommand Remote Code Execution Vulnerability. The flaw exists within the DoRcvRpcCall RPC function -exposed via the rep_srv.exe process- where the vulnerability is caused by an error when the rep_srv.exe handles a specially crafted packet sent by an unauthenticated attacker.
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 RepliStor Server Service contains a remote code execution vulnerability in the DoRcvRpcCall RPC function exposed via the rep_srv.exe process. The flaw allows unauthenticated attackers to execute arbitrary code by sending a specially crafted RPC packet to the service.
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< esa-09-003CVSS 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 EMC RepliStor is installedCheck for the presence of the RepliStor installation directory, typically under Program Files\EMC RepliStor or Program Files\Dell\EMC RepliStor, and look for rep_srv.exeAffected if The rep_srv.exe executable exists on the system
-
Confirm rep_srv.exe service is runningOpen Task Manager or use command 'tasklist /FI "IMAGENAME eq rep_srv.exe"' to check if the rep_srv.exe process is activeAffected if The rep_srv.exe process is currently running
-
Identify the installed RepliStor versionCheck the version of rep_srv.exe by right-clicking the file, selecting Properties, then viewing the Details tab for File Version, or use 'wmic product where "name like 'RepliStor%'" get version'Affected if The installed version is earlier than esa-09-003 or the version cannot be determined but the file exists
-
Verify RPC service is listeningUse 'netstat -an | findstr /i "135 139 445"' or a port scanner to check if the RPC endpoint mapper and related ports are open on the serverAffected if The RPC service ports are open and accessible from the network
The system is affected if EMC RepliStor is installed with rep_srv.exe running and the version is earlier than esa-09-003, exposing a reachable RPC service.
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 the vendor patch (ESA-09-003) or upgrade to a patched version of EMC RepliStor Server Service. If patching is not immediately possible, restrict network access to the RPC service port and disable the service until a patch can be applied.
ESA-09-003
- Identify the current version of EMC Replistor installed in the environment
- Download the ESA-09-003 patch or later version from EMC's support portal or authorized distribution channels
- Apply the ESA-09-003 patch to all affected EMC RepliStor Server installations
- Verify the patch was applied successfully by checking the version number post-installation
- Restart the rep_srv.exe service if required by the patch installation process
- Confirm the vulnerability is remediated by verifying the DoRcvRpcCall function no longer accepts specially crafted packets from unauthenticated sources
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1120 — 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-2009-1120 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