# CVE-2020-11631: Privilege escalation in n/a

> A malicious user can trigger an error state in the EJBCA CA UI to escalate privileges and execute remote code, provided specific ports lack client certificate authentication.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qc58-fx6g-366w

## What is CVE-2020-11631?

CVE-2020-11631 is a medium-severity vulnerability in n/a, published on 7 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in EJBCA before 6.15.2.6 and 7.x before 7.3.1.2. An error state can be generated in the CA UI by a malicious user. This, in turn, allows exploitation of other bugs. This follow-on exploitation can lead to privilege escalation and remote code execution. (This is exploitable only when at least one accessible port lacks a requirement for client certificate authentication. These ports are 8442 or 8080 in a standard installation.)

## Which versions are affected by CVE-2020-11631?

It affects 1 product.


Products: Primekey Ejbca.

## How do I fix CVE-2020-11631?

No fix has been published for CVE-2020-11631 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-11631 being exploited?

There is no known exploitation of CVE-2020-11631 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-34831](https://insights.sbomify.com/CVE-2022-34831/): Business logic in n/a (critical 9.8)
- [CVE-2020-11630](https://insights.sbomify.com/CVE-2020-11630/): Deserialization in n/a (critical 9.8)
- [CVE-2020-11627](https://insights.sbomify.com/CVE-2020-11627/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-25276](https://insights.sbomify.com/CVE-2020-25276/): Security feature bypass in n/a (high 7.3)
- [CVE-2020-11629](https://insights.sbomify.com/CVE-2020-11629/): File upload in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11631 and fix it if it is affected.

What it is: CVE-2020-11631 is a medium-severity vulnerability in n/a, published on 7 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11631 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-11631/ (Markdown: https://insights.sbomify.com/CVE-2020-11631/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11631
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11631
- OSV: https://osv.dev/vulnerability/CVE-2020-11631

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-11631/
Summaries are generated and may contain mistakes; the official description above is the record.