# CVE-2003-0094: Weak cryptography in n/a

> Mandrake Linux mcookie utility uses predictable entropy, weakening random number generation and potentially aiding cryptographic attacks.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vhww-qqjw-px6w

## What is CVE-2003-0094?

CVE-2003-0094 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. 

### Official description

A patch for mcookie in the util-linux package for Mandrake Linux 8.2 and 9.0 uses /dev/urandom instead of /dev/random, which causes mcookie to use an entropy source that is more predictable than expected, which may make it easier for certain types of attacks to succeed.

## Which versions are affected by CVE-2003-0094?

It affects 1 product.


Products: Andries Brouwer Util-Linux.

## How do I fix CVE-2003-0094?

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

## Is CVE-2003-0094 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2876](https://insights.sbomify.com/CVE-2005-2876/): Privilege escalation in n/a (high 7.2)
- [CVE-2001-1147](https://insights.sbomify.com/CVE-2001-1147/): Information disclosure in n/a (high 7.2)
- [CVE-2001-1175](https://insights.sbomify.com/CVE-2001-1175/): Information disclosure in n/a (high 7.2)
- [CVE-2004-0080](https://insights.sbomify.com/CVE-2004-0080/): Use after free in n/a (medium 5.0)
- [CVE-2006-7108](https://insights.sbomify.com/CVE-2006-7108/): Auth bypass in n/a (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0094 and fix it if it is affected.

What it is: CVE-2003-0094 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. 
Exploitation: There is no known exploitation of CVE-2003-0094 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-2003-0094/ (Markdown: https://insights.sbomify.com/CVE-2003-0094/index.md)
```

## Sources

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

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