# CVE-2005-0703: Auth bypass in n/a

> Remote attackers can modify system configuration via an unauthenticated account in Xerox MicroServer Web Server.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 9 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hm6q-wcc6-5fvj

## What is CVE-2005-0703?

CVE-2005-0703 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Xerox MicroServer Web Server for various WorkCentre products including M35/M45/M55 2.028.11.000 through 2.97.20.032 and 4.84.16.000 through 4.97.20.032, Pro 35/45/55 3.028.11.000 through 3.97.20.032, Pro 65/75/90 1.001.00.060 through 1.001.02.084, and others, has an "unauthenticated account," which allows remote attackers to modify system configuration, a different vulnerability than CVE-2005-1179.

## Which versions are affected by CVE-2005-0703?

It affects 18 products.


Products: Xerox Workcentre 165, Xerox Workcentre 175, Xerox Workcentre 2128, Xerox Workcentre 2636, Xerox Workcentre 32 Color, Xerox Workcentre 35, Xerox Workcentre 3545, Xerox Workcentre 40 Color, Xerox Workcentre 45, Xerox Workcentre 55, Xerox Workcentre 65, Xerox Workcentre 75, Xerox Workcentre 90, Xerox Workcentre M165, Xerox Workcentre M175, Xerox Workcentre M35, Xerox Workcentre M45, Xerox Workcentre M55.

## How do I fix CVE-2005-0703?

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

## Is CVE-2005-0703 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0703 and fix it if it is affected.

What it is: CVE-2005-0703 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Mar 2005. 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-2005-0703 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-2005-0703/ (Markdown: https://insights.sbomify.com/CVE-2005-0703/index.md)
```

## Sources

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

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