{ "data_type": "CVE", "data_format": "MITRE", "data_version": "4.0", "CVE_data_meta": { "ID": "CVE-2020-11998", "ASSIGNER": "security@apache.org", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "vendor_name": "n/a", "product": { "product_data": [ { "product_name": "Apache ActiveMQ", "version": { "version_data": [ { "version_value": "Apache Tomcat 5.15.12" } ] } } ] } } ] } }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "Arbitrary code execution via JMX" } ] } ] }, "references": { "reference_data": [ { "refsource": "MISC", "name": "http://activemq.apache.org/security-advisories.data/CVE-2020-11998-announcement.txt", "url": "http://activemq.apache.org/security-advisories.data/CVE-2020-11998-announcement.txt" } ] }, "description": { "description_data": [ { "lang": "eng", "value": "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 the 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" } ] } }