# CVE-2006-1137: Denial of service in n/a

> Remote attackers can cause a denial of service on Xerox CopyCentre and WorkCentre Pro devices by sending crafted PostScript files.

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

## What is CVE-2006-1137?

CVE-2006-1137 is a medium-severity denial of service vulnerability in n/a, published on 10 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple unspecified vulnerabilities in Xerox CopyCentre and Xerox WorkCentre Pro, running software 1.001.02.073 or earlier, or 1.001.02.074 before 1.001.02.715, allow remote attackers to cause an unspecified denial of service via a crafted PostScript file that will (1) "navigate through the directory" or (2) a "file sent to expose TCP/IP ports".

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

It affects 6 products.


Products: Xerox Copycentre C65 Firmware, Xerox Copycentre C75 Firmware, Xerox Copycentre C90 Firmware, Xerox Workcentre Pro 65 Firmware, Xerox Workcentre Pro 75 Firmware, Xerox Workcentre Pro 90 Firmware.

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

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

## Is CVE-2006-1137 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1139](https://insights.sbomify.com/CVE-2006-1139/): Information disclosure in n/a (medium 6.4)
- [CVE-2006-1138](https://insights.sbomify.com/CVE-2006-1138/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1137 is a medium-severity denial of service vulnerability in n/a, published on 10 Mar 2006. 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-2006-1137 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-1137/ (Markdown: https://insights.sbomify.com/CVE-2006-1137/index.md)
```

## Sources

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

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