# CVE-2004-2443: Auth bypass in n/a

> Remote attackers can bypass authentication in Jaws by sending a specific cookie, gaining unauthorized admin access.

- **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:** 20 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wj6r-f23g-8gv8

## What is CVE-2004-2443?

CVE-2004-2443 is a high-severity authentication bypass vulnerability in n/a, published on 20 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jaws 0.3 allows remote attackers to bypass authentication and via an HTTP request to admin.php with the logged cookie set to the MD5 hash of a null password, which is compared against the logged session variable by the logged_on function in application.php.

## Which versions are affected by CVE-2004-2443?

It affects 1 product.


Products: Jaws Jaws.

## How do I fix CVE-2004-2443?

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

## Is CVE-2004-2443 being exploited?

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

Public exploit code:

- Jaws 0.2/0.3 - Cookie Manipulation Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-3292](https://insights.sbomify.com/CVE-2006-3292/): SQL injection in n/a (high 7.5)
- [CVE-2004-2067](https://insights.sbomify.com/CVE-2004-2067/): SQL injection in n/a (high 7.5)
- [CVE-2009-0645](https://insights.sbomify.com/CVE-2009-0645/): Path traversal in n/a (medium 6.5)
- [CVE-2004-2445](https://insights.sbomify.com/CVE-2004-2445/): Path traversal in n/a (medium 5.0)
- [CVE-2005-2179](https://insights.sbomify.com/CVE-2005-2179/): Code injection in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2443 and fix it if it is affected.

What it is: CVE-2004-2443 is a high-severity authentication bypass vulnerability in n/a, published on 20 Aug 2005. 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-2004-2443 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-2004-2443/ (Markdown: https://insights.sbomify.com/CVE-2004-2443/index.md)
```

## Sources

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

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