# CVE-2006-0440: Auth bypass in n/a

> Attackers can bypass authentication and upload files by injecting an MD5 password hash into a cookie, allowing unauthorized access and file manipulation.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 26 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-876r-xj39-ff44

## What is CVE-2006-0440?

CVE-2006-0440 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Text Rider 2.4 allows attackers to bypass authentication and upload files without providing a valid password by obtaining the MD5 hash of the password (possibly via another vulnerability that reads it from a data file), then including the hash in a cookie.

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

It affects 1 product.


Products: Text Rider Text Rider.

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

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

## Is CVE-2006-0440 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0439](https://insights.sbomify.com/CVE-2006-0439/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0440 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0440 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-2006-0440/ (Markdown: https://insights.sbomify.com/CVE-2006-0440/index.md)
```

## Sources

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

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