# CVE-2004-1709: Information disclosure in n/a

> Local attackers can intercept unencrypted PINs from Datakey Rainbow iKey2032 tokens due to lack of encryption between token and driver.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6xc9-5x2c-v57j

## What is CVE-2004-1709?

CVE-2004-1709 is a low-severity vulnerability in n/a, published on 26 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Datakey Rainbow iKey2032 USB token, when using the CIP client package, does not encrypt communications between the token and the driver, which could allow local users to obtain the PINs of other users.

## Which versions are affected by CVE-2004-1709?

It affects 1 product.


Products: Datakey Rainbow Ikey2032 Usb Token.

## How do I fix CVE-2004-1709?

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

## Is CVE-2004-1709 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1709 and fix it if it is affected.

What it is: CVE-2004-1709 is a low-severity vulnerability in n/a, published on 26 Feb 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-2004-1709 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-2004-1709/ (Markdown: https://insights.sbomify.com/CVE-2004-1709/index.md)
```

## Sources

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

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