Not rated
CVE-2018-1295 In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for…
Description
In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to one of the deserialization endpoints of some Ignite components - discovery SPI, Ignite persistence, Memcached endpoint, socket steamer.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Apache Ignite | Versions not published |
References
- [dev] 20180402 [CVE-2018-1295]: Possible Execution of Arbitrary Code Within Deserialization Endpoints of Apache Ignite lists.apache.org
- RHSA-2018:2405 access.redhat.com
- 103692 www.securityfocus.com
Timeline
- Published
- Last modified
Other CVEs of Apache Ignite
The 5 CVEs of Apache Ignite →
CVE-2025-48977
Relative Path Traversal vulnerability in Apache Ignite REST API
8.5
High
CVE-2024-52577
In Apache Ignite versions from 2.6.0 and before 2.17.0, configured Class Serialization Filters are ignored for some…
9.5
Critical
CVE-2018-8018
In Apache Ignite before 2.4.8 and 2.5.x before 2.5.3, the serialization mechanism does not have a list of classes…
Not rated
CVE-2017-7686
Apache Ignite 1.0.0-RC3 to 2.0 uses an update notifier component to update the users about new project releases that…
Not rated