# CVE-2004-0004: Security feature bypass in n/a

> Remote attackers can spoof user requests by exploiting flawed signature verification in OpenCA, bypassing authentication checks.

- **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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7459-9rcq-g3xj

## What is CVE-2004-0004?

CVE-2004-0004 is a high-severity vulnerability in n/a, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The libCheckSignature function in crypto-utils.lib for OpenCA 0.9.1.6 and earlier only compares the serial of the signer's certificate and the one in the database, which can cause OpenCA to incorrectly accept a signature if the certificate's chain is trusted by OpenCA's chain directory, allowing remote attackers to spoof requests from other users.

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

It affects 1 product.


Products: Openca Openca.

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

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

## Is CVE-2004-0004 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0960](https://insights.sbomify.com/CVE-2003-0960/): Security feature bypass in n/a (high 7.5)
- [CVE-2004-0787](https://insights.sbomify.com/CVE-2004-0787/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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