CVE-2010-1941
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 · uneditedUnspecified vulnerability in NEC WebSAM DeploymentManager 5.13 and earlier, as used in SigmaSystemCenter 2.1 Update2 and earlier, BladeSystemCenter, ExpressSystemCenter, and VirtualPCCenter 2.2 and earlier, allows remote attackers to cause a denial of service (OS shutdown or restart) via unknown vectors related to Client Service for DPM and crafted packets to port 56010.
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 confidenceRemote denial of service vulnerability in NEC WebSAM DeploymentManager 5.13 and earlier allows attackers to cause OS shutdown or restart via crafted packets to port 56010 targeting the Client Service for DPM component.
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<= 2.2<= 2.1<= 2.2<= 5.13CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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 installed NEC productsReview installed software on the system for any of these NEC products: Bladesystemcenter, Expresssystemcenter, Sigmasystemcenter, Virtualpccenter, or Websam Deploymentmanager. Check Windows Add/Remove Programs or the program's installation directory for product name identification.Affected if Any of the five affected NEC products are installed on the system
-
Check product versionLocate the version information for the installed NEC product. This is typically available in the program's about dialog, installation directory, or Windows registry under the product's registry key. Compare the installed version number against the affected ranges: Bladesystemcenter and Expresssystemcenter version 2.2 or lower, Sigmasystemcenter version 2.1 or lower, Virtualpccenter version 2.2 or lower, Websam Deploymentmanager version 5.13 or lower.Affected if The installed version falls at or below the affected version thresholds for the respective product
-
Verify port 56010 statusCheck if port 56010 is listening on the system using 'netstat -an' or 'netsh firewall show all' to review firewall and port configuration. This port is required for the Client Service for DPM component that the vulnerability targets.Affected if Port 56010 is open and listening on the affected system, making it reachable for crafted packet attacks
-
Confirm Client Service for DPM is runningCheck running services on the system for the Client Service for DPM component. In Windows, use Services.msc or the 'sc query' command to enumerate active services. Look for a service related to DeploymentManager or DPM Client Service.Affected if The Client Service for DPM is actively running, which is the specific component targeted by the CVE
The system is affected if any of the five NEC products (Bladesystemcenter, Expresssystemcenter, Sigmasystemcenter, Virtualpccenter, or Websam Deploymentmanager) is installed at a version at or below the affected thresholds AND port 56010 is accessible with the Client Service for DPM running.
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.
From vendor dataUpdate to patched versions of DeploymentManager and related NEC products; alternatively, block port 56010 at network perimeter or implement network segmentation for affected systems.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1941 — 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-2010-1941 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