Red Hat Bugzilla – Bug 1559316
CVE-2018-1000130 jolokia: JMX proxy mode vulnerable to remote code execution
Last modified: 2018-09-11 03:54:26 EDT
A JNDI Injection vulnerability exists in Jolokia agent version 1.3.7 in the proxy mode that allows a remote attacker to run arbitrary Java code on the server. Note that this only affects the WAR agent, which has the proxy mode enabled by default. The JVM agent is not affected as it does not support the JMX proxy mode External References: https://jolokia.org/#Security_fixes_with_1.5.0 References: https://snyk.io/vuln/SNYK-JAVA-ORGJOLOKIA-32137
Upstream commits to support white-listing JMX service urls and fix war-agent defaults: * https://github.com/rhuss/jolokia/commit/1b360b8889f0ed51165a8d1ac55dd8e0aa2dfd4a * https://github.com/rhuss/jolokia/commit/fd7b93da30c61a45bac10d8b311f1b79a74910f5
Statement: Red Hat Product Security has rated this issue as having security impact of Low for: * Red Hat OpenStack Platform 9.0 (Mitaka) * Red Hat OpenStack Platform 10.0 (Newton) * Red Hat OpenStack Platform 11.0 (Ocata) * Red Hat OpenStack Platform 12.0 (Pike) Although the affected code is present in shipped packages, proxy mode is not enabled by default. The affected code is not used in any supported configuration of Red Hat OpenStack Platform. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
This issue has been addressed in the following products: Red Hat JBoss Fuse Via RHSA-2018:2669 https://access.redhat.com/errata/RHSA-2018:2669