# CVE-2004-0164: Missing authorization in n/a

> Remote attackers can delete certificates in the KAME IKE daemon due to improper handling of hash values in delete and INITIAL-CONTACT messages.

- **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:** Yes
- **Published:** 19 Feb 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2q54-wx6q-7cqc

## What is CVE-2004-0164?

CVE-2004-0164 is a medium-severity missing authorization vulnerability in n/a, published on 19 Feb 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

KAME IKE daemon (racoon) does not properly handle hash values, which allows remote attackers to delete certificates via (1) a certain delete message that is not properly handled in isakmp.c or isakmp_inf.c, or (2) a certain INITIAL-CONTACT message that is not properly handled in isakmp_inf.c.

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

It affects 1 product.


Products: Kame Racoon.

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

Apply the vendor's patch.

## Is CVE-2004-0164 being exploited?

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

Public exploit code:

- KAME Racoon - 'Initial Contact' SA Deletion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-0155](https://insights.sbomify.com/CVE-2004-0155/): Auth bypass in n/a (high 7.5)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0164 is a medium-severity missing authorization vulnerability in n/a, published on 19 Feb 2004. 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-0164 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-0164/ (Markdown: https://insights.sbomify.com/CVE-2004-0164/index.md)
```

## Sources

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

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