# CVE-2020-13931: Remote code execution in Apache TomEE

> Misconfigured Apache TomEE with embedded ActiveMQ exposes an unauthenticated JMX port, allowing attackers to bypass security controls.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mp28-rq7g-qx62

## What is CVE-2020-13931?

CVE-2020-13931 is a critical vulnerability in Apache TomEE, published on 17 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

If Apache TomEE 8.0.0-M1 - 8.0.3, 7.1.0 - 7.1.3, 7.0.0-M1 - 7.0.8, 1.0.0 - 1.7.5 is configured to use the embedded ActiveMQ broker, and the broker config is misconfigured, a JMX port is opened on TCP port 1099, which does not include authentication. CVE-2020-11969 previously addressed the creation of the JMX management interface, however the incomplete fix did not cover this edge case.

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

6 open source packages ship an affected version, including org.apache.tomee:apache-tomee. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomee:apache-tomee` | Maven | All versions | 7.0.9 |
| `org.apache.tomee:apache-tomee` | Maven | All versions | 7.0.9 |
| `org.apache.tomee:apache-tomee` | Maven | From 7.1.0 | 7.1.4 |
| `org.apache.tomee:apache-tomee` | Maven | From 7.1.0 | 7.1.4 |
| `org.apache.tomee:apache-tomee` | Maven | From 8.0.0 | 8.0.4 |
| `org.apache.tomee:apache-tomee` | Maven | From 8.0.0 | 8.0.4 |

Products: Apache Tomee.

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

Upgrade org.apache.tomee:apache-tomee to a fixed version for your release line: 7.0.9, 7.1.4 or 8.0.4.

## Is CVE-2020-13931 being exploited?

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

## Other vulnerabilities in Apache TomEE

- [CVE-2020-11969](https://insights.sbomify.com/CVE-2020-11969/): Missing Authentication for Critical Function in Apache TomEE (critical 9.8)
- [CVE-2019-13990](https://insights.sbomify.com/CVE-2019-13990/): XML external entity injection in Terracotta Quartz Scheduler (critical 9.8)
- [CVE-2016-0779](https://insights.sbomify.com/CVE-2016-0779/): Deserialization in n/a (critical 9.8)
- [CVE-2019-17359](https://insights.sbomify.com/CVE-2019-17359/): Out-of-Memory Error in Bouncy Castle Crypto (high 7.5)
- [CVE-2018-8031](https://insights.sbomify.com/CVE-2018-8031/): Apache TomEE console vulnerable to Cross-site Scripting (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13931 is a critical vulnerability in Apache TomEE, published on 17 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-13931 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomee:apache-tomee (Maven): affected all versions; fixed in 7.0.9
- org.apache.tomee:apache-tomee (Maven): affected all versions; fixed in 7.0.9
- org.apache.tomee:apache-tomee (Maven): affected from 7.1.0; fixed in 7.1.4
- org.apache.tomee:apache-tomee (Maven): affected from 7.1.0; fixed in 7.1.4
- org.apache.tomee:apache-tomee (Maven): affected from 8.0.0; fixed in 8.0.4
- org.apache.tomee:apache-tomee (Maven): affected from 8.0.0; fixed in 8.0.4

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-13931/ (Markdown: https://insights.sbomify.com/CVE-2020-13931/index.md)
```

## Sources

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

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