CVE-2017-15693 json
Apache Geode unsafe deserialization of application objects
published 2018-02-27 8 y ago modified 2026-06-17 4 mo ago also GHSA-95m2-p98f-24r5 , EUVD-2022-3292
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.apache.geode:geode-core 1.4.0
- apache geode 1.4.0
- github.com/apache/geode#1166 pull request
Exploit prediction
2.47% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.geode:geode-core | >=1.0.0, <1.4.0 |
1.4.0 |
Affected products
- Apache Software Foundation Apache Geode
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/apache/geode/pull/1166
web
-
securityfocus.com
/bid/103206
vdb-entry, third-party-advisory
-
lists.apache.org
/thread.html/cc3ec1d06062f54fdaa0357874c1d148fc54bb955f2d2df4ca328a3d%40%3Cuser.geode.apache.org%3E
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2017-15693
advisory
-
issues.apache.org
/jira/browse/GEODE-3923
web
-
lists.apache.org
/thread.html/cc3ec1d06062f54fdaa0357874c1d148fc54bb955f2d2df4ca328a3d@%3Cuser.geode.apache.org%3E
web
Sources
- CVE List CVE-2017-15693
- GitHub Advisory GHSA-95m2-p98f-24r5
- NVD CVE-2017-15693
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.