# CVE-2006-4680: Information disclosure in n/a

> Attackers can obtain sensitive usernames and passwords by exporting the address book from the Remote UI of Canon imageRUNNER devices.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/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:** 11 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c7cv-5w6m-27x2

## What is CVE-2006-4680?

CVE-2006-4680 is a medium-severity vulnerability in n/a, published on 11 Sep 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Remote UI in Canon imageRUNNER includes usernames and passwords when exporting an address book, which allows context-dependent attackers to obtain sensitive information.

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

It affects 7 products.


Products: Canon Imagerunner 2620, Canon Imagerunner 5020, Canon Imagerunner 6870, Canon Imagerunner 8500, Canon Imagerunner 9070, Canon Imagerunner C3220, Canon Imagerunner C6800.

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

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

## Is CVE-2006-4680 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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