Apache Geode deserialization of untrusted data flaw when using JMX over RMI on Java 11
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Geode | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
Vendor Workaround
Disable affected services such as JMX over RMI unless they are required. JMX over RMI can be disabled by setting Geode property `jmx-manager` to false; this property defaults to false on Servers and true on Locators.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-6916 | Apache Geode versions up to 1.12.2 and 1.13.2 are vulnerable to a deserialization of untrusted data flaw when using JMX over RMI on Java 11. Any user wishing to protect against deserialization attacks involving JMX or RMI should upgrade to Apache Geode 1.15. Use of 1.15 on Java 11 will automatically protect JMX over RMI against deserialization attacks. This should have no impact on performance since it only affects JMX/RMI which Gfsh uses to communicate with the JMX Manager which is hosted on a Locator. |
Github GHSA |
GHSA-qf8g-vpwp-6579 | Apache Geode versions deserialization of untrusted datawhen using JMX over RMI on Java 11 |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.5% (1.509% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.