# CVE-2006-6429: Misconfiguration in n/a

> Attackers can modify configuration settings on Xerox WorkCentre devices via the TFTP/BOOTP auto configuration option.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x2g3-p5mv-qw27

## What is CVE-2006-6429?

CVE-2006-6429 is a medium-severity vulnerability in n/a, published on 10 Dec 2006. It can be exploited over the network, with no action from the victim.

### Official description

Xerox WorkCentre and WorkCentre Pro before 12.060.17.000, 13.x before 13.060.17.000, and 14.x before 14.060.17.000 allows attackers to modify certain configuration settings via unspecified vectors involving the "TFTP/BOOTP auto configuration option."

## Which versions are affected by CVE-2006-6429?

It affects 1 product.


Products: Xerox Workcentre.

## How do I fix CVE-2006-6429?

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

## Is CVE-2006-6429 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1656](https://insights.sbomify.com/CVE-2009-1656/): Command injection in n/a (critical 10.0)
- [CVE-2008-2824](https://insights.sbomify.com/CVE-2008-2824/): Missing authorization in n/a (critical 10.0)
- [CVE-2006-6470](https://insights.sbomify.com/CVE-2006-6470/): Other in n/a (critical 10.0)
- [CVE-2006-6471](https://insights.sbomify.com/CVE-2006-6471/): Misconfiguration in n/a (critical 10.0)
- [CVE-2006-6472](https://insights.sbomify.com/CVE-2006-6472/): Misconfiguration in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6429 and fix it if it is affected.

What it is: CVE-2006-6429 is a medium-severity vulnerability in n/a, published on 10 Dec 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6429 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-2006-6429/ (Markdown: https://insights.sbomify.com/CVE-2006-6429/index.md)
```

## Sources

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

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