Security readout for executives and security teams
Plain-English summary
In specific EJBCA setups, a revoked client certificate could still be accepted for EST enrollment. If that certificate belonged to a role allowed to create new end entities, it could continue requesting new certificates. This mainly matters for organizations running EJBCA with EST enrollment and client-certificate authentication.
Executive priority
Treat as a targeted PKI control failure, not a broad internet-wide emergency. Prioritize review if EJBCA supports certificate issuance for sensitive systems or external clients through EST.
Technical view
EJBCA 6.x and 7.x before 7.4.1 did not perform revocation checks on EST client certificates during enrollment authentication. Exposure requires EST configured, client certificates used for enrollment authentication, a revoked client certificate, and that certificate retaining an authorized enrollment role.
Likely exposure
Likely limited to public key infrastructure environments using EJBCA EST enrollment with client-certificate authentication. Systems without EST, without client-certificate enrollment authentication, or without revoked certificates in enrollment-authorized roles are not described as affected.
Exploitation context
The provided sources do not report active exploitation, and this CVE is not marked KEV. Abuse depends on possession of a revoked client certificate that still maps to a role authorized to enroll new end entities.
Researcher notes
The source bundle lacks CVSS, CWE, exploit details, and broader affected-product metadata. The key condition is authorization persistence after revocation: revocation alone did not prevent EST enrollment authentication before 7.4.1.
Mitigation direction
- Upgrade EJBCA 6.x/7.x deployments to version 7.4.1 or later.
- Follow the PrimeKey advisory for deployment-specific remediation guidance.
- Before upgrade, remove revoked client certificates from their authorized roles.
- Review EST enrollment role assignments for revoked or obsolete client certificates.
Validation and detection
- Confirm whether EJBCA is running a version before 7.4.1.
- Check whether EST enrollment is configured and enabled.
- Verify whether client certificates authenticate EST enrollment.
- Identify revoked client certificates still assigned to enrollment-authorized roles.
- Review enrollment records for activity tied to revoked client certificates, if logs are available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2020-25276 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://support.primekey.com/news/posts/ejbca-security-advisory-revocation-check-not-performed-on-est-client-certificateCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.