CVE-2017-15693 Apache Geode unsafe deserialization of application objects
A user with write access can trigger remote code execution via unsafe deserialization of application objects in Apache Geode.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2017-15693?
CVE-2017-15693 is a high-severity unsafe deserialization vulnerability in Apache Geode, published on 27 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In Apache Geode before v1.4.0, the Geode server stores application objects in serialized form. Certain cluster operations and API invocations cause these objects to be deserialized. A user with DATA:WRITE access to the cluster may be able to cause remote code execution if certain classes are present on the classpath.
Weakness: CWE-502
Which versions are affected by CVE-2017-15693?
2 open source packages ship an affected version, including org.apache.geode:geode-core. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.geode:geode-core Maven | From 1.0.0 | 1.4.0 |
org.apache.geode:geode-core Maven | From 1.0.0 | 1.4.0 |
Products include Apache Geode.
How do I fix CVE-2017-15693?
Upgrade org.apache.geode:geode-core to 1.4.0 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2017-15693 being exploited?
There is no known exploitation of CVE-2017-15693 in the wild and no public exploit code.
Other vulnerabilities in Apache Geode
- CVE-2020-1938 Apache Tomcat Improper Privilege Management
- CVE-2019-15752 Docker Desktop Community Edition Privilege Escalation
- CVE-2022-37021 Apache Geode deserialization of untrusted data flaw when using JMX over RMI on Java 8.
- CVE-2014-0048 Supply chain in docker.io
- CVE-2017-15692 Apache Geode unsafe deserialization in TcpServer
Sources
Also known as GHSA-95m2-p98f-24r5.