# CVE-2004-2555: Weak cryptography in n/a

> Local attackers can calculate the Administrator password using weak cryptography if they know the Control password and recovery key.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/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:** 21 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6p5f-vq8j-gwq7

## What is CVE-2004-2555?

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

### Official description

Riverdeep FoolProof Security 3.9.x on Windows 98 and Windows ME uses weak cryptography (arithmetic and XOR operations) to relate the Control password to the Administrator password, which allows local users to calculate the Administrator password if they know the Control password and password recovery key.

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

It affects 1 product.


Products: Smartstuff Foolproof Security.

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

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

## Is CVE-2004-2555 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2555 exists.

Public exploit code:

- SmartStuff FoolProof Security Program 3.9.x - Administrative Password Recovery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0030](https://insights.sbomify.com/CVE-2001-0030/): Security feature bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2555 is a low-severity vulnerability in n/a, published on 21 Nov 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2555 exists.

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-2555/ (Markdown: https://insights.sbomify.com/CVE-2004-2555/index.md)
```

## Sources

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

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