JMX Insecure Default Configuration in GemFire
VMware Tanzu GemFire for VMs · VMware Tanzu VMware GemFire
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| VMware Tanzu VMware Tanzu GemFire for VMs |
| No fix yet |
| VMware Tanzu VMware GemFire |
| No fix yet |
VMware Tanzu GemFire for VMs · VMware Tanzu VMware GemFire
| Product | Affected | Fixed in |
|---|---|---|
| VMware Tanzu VMware Tanzu GemFire for VMs |
| No fix yet |
| VMware Tanzu VMware GemFire |
| No fix yet |
VMware GemFire versions prior to 9.10.0, 9.9.2, 9.8.7, and 9.7.6, and VMware Tanzu GemFire for VMs versions prior to 1.11.1 and 1.10.2, when deployed without a SecurityManager, contain a JMX service available which contains an insecure default configuration. This allows a malicious user to create an MLet mbean leading to remote code execution.
From the CVE record · pivotal
Affected VMware GemFire deployments without a SecurityManager expose a JMX service with an insecure default configuration. A malicious user who can access the service can create an MLet MBean, leading to remote code execution. The input does not specify whether authentication or user interaction is required.
Operators of VMware GemFire versions prior to 9.10.0, 9.9.2, 9.8.7, or 9.7.6, and VMware Tanzu GemFire for VMs versions prior to 1.11.1 or 1.10.2, should check their deployments.