CVE-2012-2290
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 NetWorker Module for Microsoft Applications (NMM) 2.2.1, 2.3 before build 122, and 2.4 before build 375 allows remote attackers to execute arbitrary code by sending a crafted message over a TCP communication channel.
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 confidenceThis is a remote code execution vulnerability in the EMC NetWorker Module for Microsoft Applications (NMM) client. Attackers can exploit the client by sending crafted TCP messages, achieving arbitrary code execution on affected systems. The vulnerability affects versions 2.2.1, 2.3 before build 122, and 2.4 before build 375.
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= 2.2.1= 2.3= 2.4CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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.
-
Verify EMC NMM is installedCheck for EMC NetWorker Module for Microsoft Applications in the system registry (under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall) or in Add/Remove ProgramsAffected if NMM is present on the system
-
Identify NMM version and build numberCheck the installed version by looking at the NMM program files directory for version information, or use the NMM client interface to view the About/Version detailsAffected if Version is 2.2.1, or version 2.3 with build lower than 122, or version 2.4 with build lower than 375
-
Confirm NMM TCP service is runningCheck if the NMM service is running and listening on network ports using netstat or by reviewing running services related to NMM or NetworkerAffected if NMM client service is active and exposed on TCP ports
-
Verify network exposureReview firewall rules or network configuration to determine if the NMM client port is accessible from untrusted networksAffected if The NMM TCP port is reachable from outside the trusted network
A system is affected if EMC NMM is installed with version 2.2.1, version 2.3 before build 122, or version 2.4 before build 375, and the NMM service is running and accessible on the network.
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 NMM to build 122 (for v2.3) or build 375 (for v2.4) or later. Additionally, restrict TCP access to the NMM client port via firewall rules or network segmentation to limit exposure to untrusted networks.
Version 2.3 build 122 or later; Version 2.4 build 375 or later (or latest supported version)
- Identify current installed version and build number of EMC NetWorker Module for Microsoft Applications
- If running version 2.3, verify the build number. If build is less than 122, upgrade to version 2.3 build 122 or later
- If running version 2.4, verify the build number. If build is less than 375, upgrade to version 2.4 build 375 or later
- For version 2.2.1, upgrade to a supported version (2.3 or 2.4 with fixed builds)
- After upgrade, verify the new build number contains the security fix
- Test the patched version in a non-production environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2290 — 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-2012-2290 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