# CVE-2001-0597: Weak cryptography in n/a

> Local attackers can recover stored passwords via brute force due to weak random seeding in the STRIP password manager for PalmOS.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 27 Jul 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-78c3-v436-q543

## What is CVE-2001-0597?

CVE-2001-0597 is a high-severity vulnerability in n/a, published on 27 Jul 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Zetetic Secure Tool for Recalling Important Passwords (STRIP) 0.5 and earlier for the PalmOS allows a local attacker to recover passwords via a brute force attack.  This attack is made feasible by STRIP's use of SysRandom, which is seeded by TimeGetTicks, and an implementation flaw which vastly reduces the password 'search space'.

## Which versions are affected by CVE-2001-0597?

It affects 1 product.


Products: Zetetic Enterprises Strip.

## How do I fix CVE-2001-0597?

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

## Is CVE-2001-0597 being exploited?

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

Public exploit code:

- Strip Password Generator 0.3/0.4/0.5 - Limited Password-Space (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0597 and fix it if it is affected.

What it is: CVE-2001-0597 is a high-severity vulnerability in n/a, published on 27 Jul 2001. 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-2001-0597 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-2001-0597/ (Markdown: https://insights.sbomify.com/CVE-2001-0597/index.md)
```

## Sources

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

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