dbcve.org
EjbcaApplication · Primekey

CVE-2020-25276

HIGH · 7.3 CVSS v3.1 Published 2020-09-11
Fix available
A fix is available. Upgrade to 7.4.1 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PrimeKey EJBCA fails to perform certificate revocation checks when using client certificates for EST protocol enrollment. A revoked certificate belonging to a role authorized to enroll new end entities can still be used for authentication, allowing continued enrollment access after the certificate should have been blocked.

MitigationRemove any revoked client certificates from their respective authorized roles, or upgrade to EJBCA 7.4.1 or later which includes the revocation check.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EjbcaApplication
Affected:>= 7.0.0, < 7.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check EJBCA installed version
    Locate the EJBCA version information in the admin web interface under 'System Configuration' > 'About', or check the version from the command line using 'jboss-cli.sh' or by examining the deployed war file name in the application server's deployment directory.
    Affected if The installed version is 7.0.0 through 7.3.x (any version >= 7.0.0 but < 7.4.1)
  2. Verify EST protocol is enabled
    In EJBCA admin web interface, navigate to 'Protocol Configuration' > 'EST' and check if the EST protocol is enabled, or review the ejbca.properties configuration file for 'est.enabled=true'.
    Affected if EST protocol is enabled and configured for use
  3. Confirm EST enrollment uses client certificate authentication
    In EJBCA admin web interface, review the EST configuration under 'Protocol Configuration' > 'EST' and check if 'Client Certificate Authentication' is set, or examine the est.properties configuration for certificate-based enrollment settings.
    Affected if EST is configured to authenticate using client certificates
  4. Identify EST-authorized roles with enrolled client certificates
    In EJBCA admin web interface, go to 'Access Control' > 'Roles' and identify roles that have EST enrollment permissions, then list the certificates bound to those roles. Alternatively, query the database tables 'RoleMember' and 'UserCertificate' to find users with EST-related roles.
    Affected if There are roles configured with EST enrollment permissions that have associated client certificates
  5. Verify revocation status of EST-authorized client certificates
    Use EJBCA's 'Search Certificates' function or query the Certificate Revocation List (CRL) distribution point to check whether any client certificates bound to EST-authorized roles appear in revocation lists, or use OpenSSL to check each certificate against the CA's CRL.
    Affected if Any client certificate authorized for EST enrollment appears in a CRL but is still assigned to an active role

You are affected if EJBCA version is 7.0.0 through 7.3.x, EST protocol is enabled with client certificate authentication, and any revoked certificates are still assigned to EST-authorized roles.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 7.4.1 or later
Fixed in 7.4.1
Interim mitigation

Remove any revoked client certificates from their respective authorized roles, or upgrade to EJBCA 7.4.1 or later which includes the revocation check.

Fix this in Ejbca Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-25276 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data