CVE-2020-11969Network attack vector

Unauthenticated JMX access via useJMX broker URI

Published Jun 15, 2020 · Updated Aug 4, 2024

Missing authentication in Apache TomEE allows remote attackers to access an exposed JMX management port over TCP port 1099. When the embedded ActiveMQ broker URI contains useJMX=true, TomEE opens the port without authentication instead of retaining the option's false default. Exposure requires that setting in 1.0.0 through 1.7.5, 7.0.0-M1 through 7.0.7, 7.1.0 through 7.1.2, or 8.0.0-M1 through 8.0.1; Apache does not identify specific MBean actions.

CVSS severity9.8
Critical
EPSS probability4.12%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Missing authentication in Apache TomEE allows remote attackers to access an exposed JMX management port over TCP port 1099. When the embedded ActiveMQ broker URI contains useJMX=true, TomEE opens the port without authentication instead of retaining the option's false default. Exposure requires that setting in 1.0.0 through 1.7.5, 7.0.0-M1 through 7.0.7, 7.1.0 through 7.1.2, or 8.0.0-M1 through 8.0.1; Apache does not identify specific MBean actions.

The record

CVE
CVE-2020-11969
Published
Jun 15, 2020
Updated
Aug 4, 2024
Vendor
Apache Software Foundation
Product
Apache TomEE
Classifications
CWE-306, CAPEC-166, CAPEC-216, CAPEC-36, CAPEC-62, CAPEC-12
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 15, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=Apache TomEE 8.0.0-M1 - 8.0.1, Apache TomEE 7.1.0 - 7.1.2, Apache TomEE 7.0.0-M1 - 7.0.7, Apache TomEE 1.0.0 - 1.7.5

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Apache Software Foundation · Apache TomEEversion=Apache TomEE 8.0.0-M1 - 8.0.1, Apache TomEE 7.1.0 - 7.1.2, Apache TomEE 7.0.0-M1 - 7.0.7, Apache TomEE 1.0.0 - 1.7.5

Published CVSS scores

6.8NIST NVDAV:N/AC:M/Au:N/C:P/I:P/A:P
9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-306Missing Authentication for Critical Function
CAPEC-166Force the System to Reset Values
CAPEC-216Communication Channel Manipulation
CAPEC-36Using Unpublished Interfaces or Functionality
CAPEC-62Cross Site Request Forgery
CAPEC-12Choosing Message Identifier

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo