# CVE-2010-2966: Hardcoded credentials in n/a

> Remote attackers can gain unauthorized access to VxWorks systems via telnet, rlogin, or FTP due to hardcoded credentials in the INCLUDE_SECURITY feature.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **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:** 16 Sep 2024
- **Also known as:** GHSA-pgq6-mhrf-p3r5

## What is CVE-2010-2966?

CVE-2010-2966 is a high-severity 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 INCLUDE_SECURITY functionality in Wind River VxWorks 6.x, 5.x, and earlier uses the LOGIN_USER_NAME and LOGIN_USER_PASSWORD (aka LOGIN_PASSWORD) parameters to create hardcoded credentials, which makes it easier for remote attackers to obtain access via a (1) telnet, (2) rlogin, or (3) FTP session.

Weakness: CWE-255

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

It affects 1 product.


Products: Windriver Vxworks.

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

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

## Is CVE-2010-2966 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0714](https://insights.sbomify.com/CVE-2013-0714/): Other in n/a (critical 10.0)
- [CVE-2021-29999](https://insights.sbomify.com/CVE-2021-29999/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-38346](https://insights.sbomify.com/CVE-2023-38346/): Path traversal in n/a (high 8.8)
- [CVE-2019-9865](https://insights.sbomify.com/CVE-2019-9865/): Integer overflow in n/a (high 8.1)
- [CVE-2015-7599](https://insights.sbomify.com/CVE-2015-7599/): Integer overflow in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2966 is a high-severity 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-2966 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-2966/ (Markdown: https://insights.sbomify.com/CVE-2010-2966/index.md)
```

## Sources

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

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