# CVE-2008-7113: Auth bypass in n/a

> Remote attackers can bypass access controls and upload documents to Kyocera Mita scanners by brute-forcing predictable user identification numbers.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fgqj-3gr4-p3fv

## What is CVE-2008-7113?

CVE-2008-7113 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Aug 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Scanner File Utility (aka listener) in Kyocera Mita (KM) 3.3.0.1 uses a small space of predictable user identification numbers for access control, which allows remote attackers to upload documents via a brute force attack.

Weakness: CWE-310

## Which versions are affected by CVE-2008-7113?

It affects 1 product.


Products: Kyoceramita Scanner File Utility.

## How do I fix CVE-2008-7113?

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

## Is CVE-2008-7113 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7109](https://insights.sbomify.com/CVE-2008-7109/): Auth bypass in n/a (critical 9.8)
- [CVE-2008-7111](https://insights.sbomify.com/CVE-2008-7111/): File upload in n/a (critical 9.3)
- [CVE-2008-7110](https://insights.sbomify.com/CVE-2008-7110/): Path traversal in n/a (high 7.8)
- [CVE-2008-7112](https://insights.sbomify.com/CVE-2008-7112/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-7113 and fix it if it is affected.

What it is: CVE-2008-7113 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Aug 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-7113 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-2008-7113/ (Markdown: https://insights.sbomify.com/CVE-2008-7113/index.md)
```

## Sources

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

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