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

> Remote attackers can bypass authentication in CVS servers using the repouid patch via the pserver access method.

- **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:** Yes
- **Published:** 27 Apr 2005
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2004-1342, GHSA-j35r-wwj5-v97h

## What is CVE-2004-1342?

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

### Official description

CVS 1.12 and earlier on Debian GNU/Linux, when using the repouid patch, allows remote attackers to bypass authentication via the pserver access method.

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

It affects 1 product.


Products: Cvs Cvs.

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

Apply the vendor's patch.

## Is CVE-2004-1342 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0804](https://insights.sbomify.com/CVE-2012-0804/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0414](https://insights.sbomify.com/CVE-2004-0414/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0416](https://insights.sbomify.com/CVE-2004-0416/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0418](https://insights.sbomify.com/CVE-2004-0418/): Memory corruption in n/a (critical 10.0)
- [CVE-2005-0753](https://insights.sbomify.com/CVE-2005-0753/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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