Search for packages
| purl | pkg:maven/org.apache.activemq/activemq-parent@5.15.12 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-pe37-xakm-3qb4
Aliases: CVE-2020-11998 GHSA-wqfh-9m4g-7x6x |
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') 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 |
Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-a3nb-p5p6-zbf7 | Missing Authentication for Critical Function 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. |
CVE-2020-13920
GHSA-xgrx-xpv2-6vp4 |