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

> Remote attackers can brute force weak passwords generated from account names to modify user credentials in the iBill password management system.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-r5wp-92q4-r3r8

## What is CVE-2001-0839?

CVE-2001-0839 is a high-severity vulnerability in n/a, published on 22 Nov 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ibillpm.pl in iBill password management system generates weak passwords based on a client's MASTER_ACCOUNT, which allows remote attackers to modify account information in the .htpasswd file via brute force password guessing.

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

It affects 1 product.


Products: Ibill Internet Billing Company Processing Plus.

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

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

## Is CVE-2001-0839 being exploited?

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

Public exploit code:

- iBill Management Script - Weak Hard-Coded Password (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0839 is a high-severity vulnerability in n/a, published on 22 Nov 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0839 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-0839/ (Markdown: https://insights.sbomify.com/CVE-2001-0839/index.md)
```

## Sources

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

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