# CVE-2006-0788: Auth bypass in n/a

> Remote attackers can bypass authentication to read and modify configuration settings on Kyocera FS-3830N printers via a hidden backdoor string.

- **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:** 19 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fqhp-q65q-7rff

## What is CVE-2006-0788?

CVE-2006-0788 is a medium-severity authentication bypass vulnerability in n/a, published on 19 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kyocera 3830 (aka FS-3830N) printers have a back door that allows remote attackers to read and alter configuration settings via strings that begin with "!R!SIOP0", as demonstrated using (1) a connection to to TCP port 9100 or (2) the UNIX lp command.

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

It affects 1 product.


Products: Kyocera Fs-3830n.

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

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

## Is CVE-2006-0788 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0789](https://insights.sbomify.com/CVE-2006-0789/): Hardcoded credentials in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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