# CVE-2005-2209: Information disclosure in n/a

> Local users can read sensitive passwords stored in cleartext in the configuration file of Capturix ScanShare.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cv78-f6r2-g223

## What is CVE-2005-2209?

CVE-2005-2209 is a medium-severity vulnerability in n/a, published on 11 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Capturix ScanShare 1.06 build 50 stores sensitive information such as the password in cleartext in capturixss_cfg.ini, which is readable by local users.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Capturix Scanshare.

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

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

## Is CVE-2005-2209 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2209 is a medium-severity vulnerability in n/a, published on 11 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2209 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-2209/ (Markdown: https://insights.sbomify.com/CVE-2005-2209/index.md)
```

## Sources

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

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