Security readout for executives and security teams
Plain-English summary
EJBCA deployments before 7.6.0 could let one authorized CMP RA tenant revoke another tenant’s certificate. That can disrupt certificate-based access or trust relationships. Exposure appears limited to systems using CMP RA Mode with a known client certificate authentication model.
Executive priority
Treat as a focused but important PKI control issue. Prioritize remediation for multi-tenant EJBCA environments because unauthorized revocation can interrupt certificate-dependent services, customer access, or trust operations.
Technical view
In CMP RA Mode, EJBCA could authenticate revocation requests with the same RA client certificate used for enrollment. Enrollment checked CA and profile tenant access, but revocation did not, allowing cross-tenant certificate revocation by a known tenant.
Likely exposure
Likely exposed systems are PrimeKey EJBCA versions before 7.6.0 using CMP RA Mode configured with known client certificate authentication, especially multi-tenant CA environments where revocation is delegated through RA clients.
Exploitation context
The source bundle does not identify public exploitation, and the CVE is not listed as KEV. Abuse requires a known tenant or RA client credential with access to the CMP RA revocation path, not unauthenticated internet access based on the provided evidence.
Researcher notes
The affected metadata in the bundle is sparse and CVSS/CWE details are absent. The core issue is authorization inconsistency: enrollment enforces tenant constraints, while revocation authentication omitted the same tenant access check before 7.6.0.
Mitigation direction
- Upgrade EJBCA to 7.6.0 or later, following vendor guidance.
- Review PrimeKey advisory details before applying production changes.
- Disable CMP RA Mode where it is not required.
- Use tenant-separated RA credentials and revocation permissions where possible.
- Monitor certificate revocation events for cross-tenant anomalies.
Validation and detection
- Inventory EJBCA versions and identify instances older than 7.6.0.
- Confirm whether CMP RA Mode is enabled.
- Check whether known client certificates authenticate RA revocation requests.
- Review audit logs for revocations affecting other tenants.
- Validate revocation authorization is tenant-scoped after remediation.
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-2021-40088 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/51CVE 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.