Description
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. Upgrade to Apache ActiveMQ 5.15.12.
Remediation
References
http://activemq.apache.org/security-advisories.data/CVE-2020-13920-announcement.txt
https://lists.apache.org/thread.html/r946488fb942fd35c6a6e0359f52504a558ed438574a8f14d36d7dcd7%40%3Ccommits.activemq.apache.org%3E
https://lists.apache.org/thread.html/rb2fd3bf2dce042e0ab3f3c94c4767c96bb2e7e6737624d63162df36d%40%3Ccommits.activemq.apache.org%3E
https://lists.debian.org/debian-lts-announce/2020/10/msg00013.html
https://lists.debian.org/debian-lts-announce/2023/11/msg00013.html
https://www.oracle.com/security-alerts/cpuoct2020.html
Related Vulnerabilities
CVE-2015-5262 Vulnerability in maven package org.apache.httpcomponents:httpclient
CVE-2023-31066 Vulnerability in maven package org.apache.inlong:manager-service
CVE-2017-2585 Vulnerability in maven package org.keycloak:keycloak-server-spi-private
CVE-2018-1000136 Vulnerability in npm package electron
CVE-2023-43496 Vulnerability in maven package org.jenkins-ci.main:jenkins-core