====================================================================

                             CERT-Renater

                 Note d'Information No. 2020/VULN508
_____________________________________________________________________

DATE                : 11/09/2020

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running Apache ActiveMQ versions prior to
                                     5.15.13.

=====================================================================
http://mail-archives.apache.org/mod_mbox/activemq-users/202009.mbox/%3c2A06806A-5F35-436B-9D62-53AF557309A8@nanthrax.net%3e
http://mail-archives.apache.org/mod_mbox/activemq-users/202009.mbox/%3c2EEDB492-CE9B-419A-AFAD-983EC32783F3@nanthrax.net%3e
_____________________________________________________________________

CVE-2020-11998: Apache ActiveMQ JMX remote client could execute
arbitrary code

Severity: Moderate

Vendor: The Apache Software Foundation

Affected Version: only Apache ActiveMQ 5.15.12

Vulnerability details:
A regression has been introduced in the commit preventing JMX re-bind.
By passing an empty environment map to RMIConnectorServer, instead of
the map that contains he authentication credentials, it leaves ActiveMQ
open to the following attack:

 https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html

"A remote client could create a javax.management.loading.MLet MBean and
use it to create new MBeans from arbitrary URLs, at least if there is no
security manager. In other words, a rogue remote client could make your
Java application execute arbitrary code."

Mitigation: Upgrade to Apache ActiveMQ 5.15.13

Credit: Jonathan Gallimore & Colm O hEigeartaigh
_____________________________________________________________________


CVE-2020-13920: Apache ActiveMQ JMX is vulnerable to a MITM attack

Severity: Moderate

Vendor: The Apache Software Foundation

Affected Version: Apache ActiveMQ version prior to 5.15.12

Vulnerability details:
Apache ActiveMQ uses LocateRegistry.createRegistry() to create the JMX
RMI registry and binds the server to the "jmxrmi" entry. It is possible
to connect to the registry without authentication and call the rebind
method to rebind jmxrmi to something else. If an attacker creates
another server to proxy the original, and bound that, he effectively
becomes a man in the middle and is able to intercept the credentials
when an user connects.


Mitigation:
Upgrade to Apache ActiveMQ 5.15.12

Credit: Jonathan Gallimore & Colm O hEigeartaigh

_____________________________________________________________________




=========================================================
+ CERT-RENATER       |    tel : 01-53-94-20-44          +
+ 23/25 Rue Daviel   |    fax : 01-53-94-20-41          +
+ 75013 Paris        |    email:cert@support.renater.fr +
=========================================================