# CVE-2020-11629: File upload in n/a

> An attacker with CA UI access can upload malicious scripts via the External Command Certificate Validator, leading to code execution on the server.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gvrc-hmg2-fp39

## What is CVE-2020-11629?

CVE-2020-11629 is a high-severity vulnerability in n/a, published on 7 Apr 2020. An attacker needs administrator access to exploit it, 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. The External Command Certificate Validator, which allows administrators to upload external linters to validate certificates, is supposed to save uploaded test certificates to the server. An attacker who has gained access to the CA UI could exploit this to upload malicious scripts to the server. (Risks associated with this issue alone are negligible unless a malicious user already has gained access to the CA UI through other means, as a trusted user is already trusted to upload scripts by virtue of having access to the validator.)

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Primekey Ejbca.

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

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

## Is CVE-2020-11629 being exploited?

There is no known exploitation of CVE-2020-11629 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-11631](https://insights.sbomify.com/CVE-2020-11631/): Privilege escalation in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11629 is a high-severity vulnerability in n/a, published on 7 Apr 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11629 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-11629/ (Markdown: https://insights.sbomify.com/CVE-2020-11629/index.md)
```

## Sources

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

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