# CVE-2020-25276: Security feature bypass in n/a

> Attackers can bypass certificate revocation checks during EST enrollment if client certificates are used, allowing revoked certificates to enroll new entities.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-ejbca-2020-25276, GHSA-h4c3-p5w7-477x

## What is CVE-2020-25276?

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

### Official description

An issue was discovered in PrimeKey EJBCA 6.x and 7.x before 7.4.1. When using a client certificate to enroll over the EST protocol, no revocation check is performed on that certificate. This vulnerability can only affect a system that has EST configured, uses client certificates to authenticate enrollment, and has had such a certificate revoked. This certificate needs to belong to a role that is authorized to enroll new end entities. (To completely mitigate this problem prior to upgrade, remove any revoked client certificates from their respective roles.)

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2020-25276?

1 open source package ship an affected version, including ejbca. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ejbca` | Bitnami | From 7.0.0 | 7.4.1 |

Products: Primekey Ejbca.

## How do I fix CVE-2020-25276?

Upgrade ejbca to 7.4.1 or later.

## Is CVE-2020-25276 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-34831](https://insights.sbomify.com/CVE-2022-34831/): Business logic in n/a (critical 9.8)
- [CVE-2020-11630](https://insights.sbomify.com/CVE-2020-11630/): Deserialization in n/a (critical 9.8)
- [CVE-2020-11627](https://insights.sbomify.com/CVE-2020-11627/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-11629](https://insights.sbomify.com/CVE-2020-11629/): File upload in n/a (high 7.2)
- [CVE-2020-11631](https://insights.sbomify.com/CVE-2020-11631/): Privilege escalation in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25276 and fix it if it is affected.

What it is: CVE-2020-25276 is a high-severity vulnerability in n/a, published on 11 Sep 2020. 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-2020-25276 in the wild and no public exploit code.

Affected packages and fixed versions:
- ejbca (Bitnami): affected from 7.0.0; fixed in 7.4.1

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-2020-25276/ (Markdown: https://insights.sbomify.com/CVE-2020-25276/index.md)
```

## Sources

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

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