dbcve.org
EjbcaApplication · Primekey

CVE-2020-11628

MEDIUM · 5.3 CVSS v3.1 Published 2020-04-08
Fix available
A fix is available. Upgrade to 6.15.2.6 / 7.3.1.2 or later.
See remediation →
62/100
Remediation priority · Elevated
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 EJBCA before 6.15.2.6 and 7.x before 7.3.1.2. It is intended to support restriction of available remote protocols (CMP, ACME, REST, etc.) through the system configuration. These restrictions can be bypassed by modifying the URI string from a client. (EJBCA's internal access control restrictions are still in place, and each respective protocol must be configured to allow for enrollment.)

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

EJBCA versions before 6.15.2.6 and 7.x before 7.3.1.2 have a protocol restriction bypass vulnerability. The system's intended controls for limiting remote protocols (CMP, ACME, REST) can be circumvented by modifying the URI string in client requests, allowing access to protocols that should be restricted at the configuration level.

MitigationUpgrade EJBCA to version 6.15.2.6, 7.3.1.2, or later. Review protocol configurations and internal access control settings to ensure restricted protocols are properly disabled unless explicitly needed.

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:< 6.15.2.6>= 7.0.0, < 7.3.1.2

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
None
Availability
None

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

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. Identify EJBCA installation version
    Check the installed EJBCA version by reviewing the application deployment documentation, startup logs, or administrative interface. Common locations include the admin panel or version file in the application directory.
    Affected if The installed version is below 6.15.2.6, or is 7.0.0 through 7.3.1.1 (including 7.0.x, 7.1.x, 7.2.x, 7.3.0, and 7.3.1.0).
  2. Review CMP protocol configuration
    Access the EJBCA administrative interface or configuration files and inspect the CMP (Certificate Management Protocol) settings. Determine whether CMP is enabled and whether protocol restrictions are configured to limit remote access.
    Affected if CMP protocol is enabled and accessible from untrusted networks, and the version is within the affected range.
  3. Review ACME protocol configuration
    Access the EJBCA administrative interface or configuration files and inspect the ACME (Automated Certificate Management Environment) settings. Check whether ACME is enabled and if protocol restrictions are applied.
    Affected if ACME protocol is enabled and accessible from untrusted networks, and the version is within the affected range.
  4. Review REST protocol configuration
    Access the EJBCA administrative interface or configuration files and inspect the REST (Representational State Transfer) API settings. Verify whether REST services are enabled and whether access controls are properly restricted.
    Affected if REST API is enabled and accessible from untrusted networks, and the version is within the affected range.
  5. Inspect URI-based request handling
    If logs or network traces are available, examine how the EJBCA server handles URI strings in incoming requests. Look for evidence of modified URI strings that may have bypassed configured protocol restrictions.
    Affected if Logs or traffic analysis show URI manipulation attempts, or protocol restrictions are unexpectedly allowing connections that should be blocked based on configuration.

You are affected if your EJBCA version falls within the vulnerable range (< 6.15.2.6 or >= 7.0.0, < 7.3.1.2) and any of the CMP, ACME, or REST protocols are enabled and accessible from untrusted networks.

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 6.15.2.6 / 7.3.1.2 or later
Fixed in 6.15.2.67.3.1.2
Interim mitigation

Upgrade EJBCA to version 6.15.2.6, 7.3.1.2, or later. Review protocol configurations and internal access control settings to ensure restricted protocols are properly disabled unless explicitly needed.

Fix this in Ejbca Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11628 — 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-11628 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