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

> Remote attackers can bypass authentication and conduct man-in-the-middle attacks by exploiting missing RSA signature verification in the Racoon IKE daemon.

- **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:** 16 Apr 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-m5jg-5w4m-4mhc

## What is CVE-2004-0155?

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

### Official description

The KAME IKE Daemon Racoon, when authenticating a peer during Phase 1, validates the X.509 certificate but does not verify the RSA signature authentication, which allows remote attackers to establish unauthorized IP connections or conduct man-in-the-middle attacks using a valid, trusted X.509 certificate.

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

It affects 1 product.


Products: Kame Racoon.

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

Apply the vendor's patch.

## Is CVE-2004-0155 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0392](https://insights.sbomify.com/CVE-2004-0392/): Denial of service in n/a (medium 5.0)
- [CVE-2004-0403](https://insights.sbomify.com/CVE-2004-0403/): Denial of service in n/a (medium 5.0)
- [CVE-2004-0164](https://insights.sbomify.com/CVE-2004-0164/): Missing authorization in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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