CVE-2020-13931

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.

Published: 2020-12-17 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-13931 is rated High Risk (72.3/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 3.65%). EPSS rose +2.30% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-13931

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 1.35% 3.65% +2.30%
2 2025-05-31 1.83% 1.35% -0.47%
3 2025-03-30 — 1.83% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-13931

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2020-13931

GitHub Security Advisory for CVE-2020-13931

GHSA-mp28-rq7g-qx62 · Severity: critical · Ecosystem: maven — Remote code execution in Apache TomEE

Affected software / configurations for CVE-2020-13931

Vendor Product Version Raw CPE
apache tomee >= 1.0.0, <= 1.7.5 cpe:2.3:a:apache:tomee:*:*:*:*:*:*:*:*
apache tomee >= 7.0.0, <= 7.0.8 cpe:2.3:a:apache:tomee:*:*:*:*:*:*:*:*
apache tomee >= 7.1.0, <= 7.1.3 cpe:2.3:a:apache:tomee:*:*:*:*:*:*:*:*
apache tomee >= 8.0.0, <= 8.0.3 cpe:2.3:a:apache:tomee:*:*:*:*:*:*:*:*
apache tomee 7.0.0 cpe:2.3:a:apache:tomee:7.0.0:m1:*:*:*:*:*:*
apache tomee 7.0.0 cpe:2.3:a:apache:tomee:7.0.0:m2:*:*:*:*:*:*
apache tomee 7.0.0 cpe:2.3:a:apache:tomee:7.0.0:m3:*:*:*:*:*:*
apache tomee 8.0.0 cpe:2.3:a:apache:tomee:8.0.0:m1:*:*:*:*:*:*

References for CVE-2020-13931

cvelogic Threat Intelligence