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

> Administrators can escalate privileges to Unix root via the web interface, allowing full system compromise.

- **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:** 11 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-78j9-3m69-vxv3

## What is CVE-2020-12713?

CVE-2020-12713 is a high-severity vulnerability in n/a, published on 11 Jun 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in CipherMail Community Gateway and Professional/Enterprise Gateway 1.0.1 through 4.7.1-0 and CipherMail Webmail Messenger 1.1.1 through 3.1.1-0. Attackers with administrative access to the web interface have multiple options to escalate their privileges to the Unix root account.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 2 products.


Products: Ciphermail Gateway, Ciphermail Webmail Messenger.

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

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

## Is CVE-2020-12713 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12714](https://insights.sbomify.com/CVE-2020-12714/): Weak cryptography in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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