# CVE-2000-1008: Weak cryptography in n/a

> Weak encryption in PalmOS allows attackers with physical access to decrypt user passwords and gain unauthorized device access.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 29 Nov 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v3w6-x84c-6p75

## What is CVE-2000-1008?

CVE-2000-1008 is a medium-severity vulnerability in n/a, published on 29 Nov 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PalmOS 3.5.2 and earlier uses weak encryption to store the user password, which allows attackers with physical access to the Palm device to decrypt the password and gain access to the device.

## Which versions are affected by CVE-2000-1008?

It affects 1 product.


Products: Palm Palm Os.

## How do I fix CVE-2000-1008?

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

## Is CVE-2000-1008 being exploited?

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

Public exploit code:

- Palm OS 3.5.2 - Weak Encryption (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-4213](https://insights.sbomify.com/CVE-2007-4213/): Denial of service in n/a (high 7.1)
- [CVE-2002-0116](https://insights.sbomify.com/CVE-2002-0116/): Denial of service in n/a (medium 5.0)
- [CVE-2001-0157](https://insights.sbomify.com/CVE-2001-0157/): Auth bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-1008 and fix it if it is affected.

What it is: CVE-2000-1008 is a medium-severity vulnerability in n/a, published on 29 Nov 2000. 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-2000-1008 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-2000-1008/ (Markdown: https://insights.sbomify.com/CVE-2000-1008/index.md)
```

## Sources

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

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