# CVE-2010-2965: Missing authorization in n/a

> Remote attackers can read or modify arbitrary memory and execute code on Rockwell Automation modules via the exposed VxWorks debug service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2010
- **Updated:** 28 May 2026
- **Also known as:** GHSA-4hhv-jc45-cmpc

## What is CVE-2010-2965?

CVE-2010-2965 is a critical missing authorization vulnerability in n/a, published on 4 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2010-2965?

It affects 2 products.


Products: Rockwellautomation 1756-Enbt\/a Firmware, Windriver Vxworks.

## How do I fix CVE-2010-2965?

No fix has been published for CVE-2010-2965 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-2965 being exploited?

There is no known exploitation of CVE-2010-2965 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2965 and fix it if it is affected.

What it is: CVE-2010-2965 is a critical missing authorization vulnerability in n/a, published on 4 Aug 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-2965 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-2965/ (Markdown: https://insights.sbomify.com/CVE-2010-2965/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-2965
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-2965
- OSV: https://osv.dev/vulnerability/CVE-2010-2965

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-2965/
Summaries are generated and may contain mistakes; the official description above is the record.