CVE-2020-5396
JMX Insecure Default Configuration in GemFire
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.10.2, 1.11.1, 9.7.6, 9.8.7, 9.9.2, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- VMware Tanzu VMware Tanzu GemFire for VMs
From 1.10 · fixed in 1.10.2; From 1.11 · fixed in 1.11.1
- VMware Tanzu VMware GemFire
From 9.7 · fixed in 9.7.6; From 9.8 · fixed in 9.8.7; From 9.9 · fixed in 9.9.2; From 9.10 · fixed in 9.10.0