CVE-2010-0775
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 IBM WebSphere Application Server (WAS) 6.0 before 6.0.2.41, 6.1 before 6.1.0.31, and 7.0 before 7.0.0.11 allows remote attackers to cause a denial of service (memory consumption and daemon crash) via a crafted request, related to the nodeagent and Deployment Manager components.
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 confidenceUnspecified vulnerability in IBM WebSphere Application Server allows remote attackers to cause denial of service through memory consumption and daemon crash via crafted requests targeting the nodeagent and Deployment Manager components.
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= 6.0= 6.0.0.1= 6.0.0.2= 6.0.0.3= 6.0.1= 6.0.1.1= 6.0.1.2= 6.0.1.3= 6.0.1.5= 6.0.1.7= 6.0.1.9= 6.0.1.11CVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 WebSphere versionRun the WebSphere versionInfo command from the installation bin directory: ./versionInfo.sh (Linux/Unix) or versionInfo.bat (Windows). Alternatively, check the product.registry file in the WebSphere installation directory.Affected if The displayed version matches any of these: 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.1.0, 6.1.0.1, 6.1.0.2, 6.1.0.3, 6.1.0.5, 6.1.0.7, 6.1.0.9, 6.1.0.11.
-
Confirm nodeagent process is runningOn the node agent system, use the ps command (ps -ef | grep nodeagent) or check the WebSphere administrative console under Servers > Node Agents, or query via wsadmin scripting.Affected if A nodeagent process is active and listed in the WebSphere administration console.
-
Confirm Deployment Manager is runningOn the Deployment Manager system, use the ps command (ps -ef | grep deploymentmanager) or check the WebSphere administrative console under System Administration > Deployment Manager, or query via wsadmin scripting.Affected if A Deployment Manager process is active and listed in the WebSphere administration console.
-
Check network exposure of nodeagentRun netstat or ss commands to check if the nodeagent SOAP or RMI ports (default 9800-9810 range or custom configured) are listening on non-loopback interfaces. Inspect the serverindex.xml file in the node profile config directory for port definitions.Affected if The nodeagent ports are bound to 0.0.0.0 or a routable IP address rather than localhost only.
-
Check network exposure of Deployment ManagerRun netstat or ss commands to check if the Deployment Manager SOAP or RMI ports are listening on non-loopback interfaces. Inspect the serverindex.xml file in the dmgr profile config directory for port definitions.Affected if The Deployment Manager ports are bound to 0.0.0.0 or a routable IP address rather than localhost only.
You are affected if you run any of the listed WebSphere versions (6.0.x or 6.1.0.x) with nodeagent or Deployment Manager components exposed 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.
From vendor dataApply IBM WebSphere patches 6.0.2.41, 6.1.0.31, or 7.0.0.11 (or upgrade to later supported versions) to resolve the vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0775 — 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-0775 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