# CVE-2010-0101: Denial of service in n/a

> Remote attackers can cause a denial of service on Lexmark printers by sending a malformed HTTP Authorization header to the embedded server.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-r3cr-84p4-932f

## What is CVE-2010-0101?

CVE-2010-0101 is a high-severity denial of service vulnerability in n/a, published on 4 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The embedded HTTP server in multiple Lexmark laser and inkjet printers and MarkNet devices, including X94x, W840, T656, N4000, E462, C935dn, 25xxN, and other models, allows remote attackers to cause a denial of service (operating system halt) via a malformed HTTP Authorization header.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 61 products.


Products: Lexmark 25xxn, Lexmark C510, Lexmark C52x, Lexmark C53x, Lexmark C540, Lexmark C543, Lexmark C544, Lexmark C546, Lexmark C73x, Lexmark C77x, Lexmark C78x, Lexmark C920, Lexmark C935dn, Lexmark E120, Lexmark E238, Lexmark E23x, Lexmark E240, Lexmark E240n, Lexmark E250, Lexmark E260 and 41 more.

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

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

## Is CVE-2010-0101 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6032](https://insights.sbomify.com/CVE-2013-6032/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0101 is a high-severity denial of service vulnerability in n/a, published on 4 May 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-0101 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-0101/ (Markdown: https://insights.sbomify.com/CVE-2010-0101/index.md)
```

## Sources

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

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