CVE-2010-2965
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 WDB target agent debug service in Wind River VxWorks 6.x, 5.x, and earlier, as used on the Rockwell Automation 1756-ENBT series A with firmware 3.2.6 and 3.6.1 and other products, allows remote attackers to read or modify arbitrary memory locations, perform function calls, or manage tasks via requests to UDP port 17185, a related issue to CVE-2005-3804.
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 WDB (Wind Debug) target agent debug service in Wind River VxWorks 6.x, 5.x and earlier contains an unauthenticated remote code execution vulnerability. The debug service listens on UDP port 17185 and allows remote attackers to read/write arbitrary memory locations, perform function calls, and manage tasks, effectively providing complete control over the affected device.
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= 3.2.6= 3.6.1<= 6.9.4.12CVSS 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 UDP port 17185 is listeningRun a network port scan or check listening ports on the device: `netstat -anu | grep 17185` or `nmap -sU -p 17185 <target>`Affected if UDP port 17185 is open and accepting connections - this indicates the WDB debug service is running
-
Identify the VxWorks versionQuery the device for its OS version through SNMP, HTTP management interface, or proprietary protocols: `snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1991.1` or check firmware/diagnostics pagesAffected if The installed VxWorks version is 6.x, 5.x, or earlier, or falls at or below 6.9.4.12
-
Identify 1756-ENBT/A firmware versionFor Rockwell Automation devices, query the module via EtherNet/IP or check the control logix firmware revision: `svcl -d <controller> -m 1756-ENBT` or use RSLinx to view module revisionAffected if The 1756-ENBT/A firmware is exactly version 3.2.6 or 3.6.1
-
Confirm network accessibility of the debug portVerify the device with port 17185 exposed is reachable from network segments outside the trusted development zoneAffected if UDP port 17185 is reachable from untrusted network segments - the vulnerability is remotely exploitable
A system is affected if it runs VxWorks 6.x/5.x or <= 6.9.4.12, or uses 1756-ENBT/A firmware 3.2.6 or 3.6.1, and has UDP port 17185 open and 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.
From vendor dataBlock UDP port 17185 at network perimeter firewalls, disable the WDB debug service if not required for development, and apply vendor firmware updates for affected devices such as the Rockwell Automation 1756-ENBT series.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2965 — 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-2965 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