# CVE-2006-4068: Weak cryptography in n/a

> Weak client-side hashing in pswd.js allows remote attackers to bypass authentication via offline brute force or collision 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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5jmg-gc72-rrxh

## What is CVE-2006-4068?

CVE-2006-4068 is a medium-severity vulnerability in n/a, published on 10 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The pswd.js script relies on the client to calculate whether a username and password match hard-coded hashed values for a server, and uses a hashing scheme that creates a large number of collisions, which makes it easier for remote attackers to conduct offline brute force attacks.  NOTE: this script might also allow attackers to generate the server-side "secret" URL without determining the original password, but this possibility was not discussed by the original researcher.

Weakness: CWE-255

## Which versions are affected by CVE-2006-4068?

It affects 1 product.


Products: Pswd.js Pswd.js.

## How do I fix CVE-2006-4068?

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

## Is CVE-2006-4068 being exploited?

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

Public exploit code:

- PSWD.JS - Insecure Password Hash (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4068 and fix it if it is affected.

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

## Sources

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

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