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…

published December 17, 2020

CVSS
—
EPSS
4%
Percentile
89.7
In the wild
Unconfirmed
What it is

🚨 A misconfigured JMX port is just waiting to be discovered; it's like leaving the front door wide open while you run off to the grocery store! Think of this vulnerability like a hotel with a lobby that has no front desk — anyone can waltz in and access sensitive areas without checking in. Just as you wouldn’t want random guests roaming through your room, you definitely don’t want unauthorized users accessing your server’s management interface. Without authentication on the JMX port at TCP 1099, an attacker could gain unrestricted access to manage and control your Apache TomEE instance. This could lead to devastating consequences, such as altering settings, viewing sensitive data, or even taking full control of your system. The potential for chaos is absolutely mind-blowing!

Put simply

Think of this vulnerability like a hotel with a lobby that has no front desk — anyone can waltz in and access sensitive areas without checking in. Just as you wouldn’t want random guests roaming through your room, you definitely don’t want unauthorized users accessing your server’s management interface. This vulnerability arises when Apache TomEE versions 8.0.0-M1 to 8.0.3, 7.1.0 to 7.1.3, and 7.0.0-M1 to 7.0.8 are configured with an embedded ActiveMQ broker without proper authentication, leaving the JMX management interface exposed on TCP port 1099.

What to do

Without authentication on the JMX port at TCP 1099, an attacker could gain unrestricted access to manage and control your Apache TomEE instance. This could lead to devastating consequences, such as altering settings, viewing sensitive data, or even taking full control of your system. The potential for chaos is absolutely mind-blowing! To remediate this vulnerability, ensure that the JMX port is properly secured with authentication or disable the JMX management interface entirely if it's not needed. Also, consider updating to the latest version of Apache TomEE that addresses this issue to minimize your risk. You've got this! With a little attention to configuration, you can safeguard your server and keep those pesky intruders out! 🛡️

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.03699 · 89.7th percentile
Published
2020-12-17T23:42Z
EPSS history
Timeline
  • 17 DEC 23:42Z
    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…
    cvelistv5