# CVE-2003-0960: Security feature bypass in n/a

> OpenCA fails to correctly validate certificate chains, allowing attackers to use revoked or expired certificates to bypass security 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:** 2 Dec 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g666-8cmc-c2x7

## What is CVE-2003-0960?

CVE-2003-0960 is a high-severity vulnerability in n/a, published on 2 Dec 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenCA before 0.9.1.4 does not use the correct certificate in a chain to check the serial, which could cause OpenCA to accept revoked or expired certificates.

## Which versions are affected by CVE-2003-0960?

It affects 1 product.


Products: Openca Openca.

## How do I fix CVE-2003-0960?

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

## Is CVE-2003-0960 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0004](https://insights.sbomify.com/CVE-2004-0004/): 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-2003-0960 and fix it if it is affected.

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

## Sources

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

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