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.
References
Link | Resource |
---|---|
http://www.securityfocus.com/bid/103692 | Third Party Advisory VDB Entry |
https://access.redhat.com/errata/RHSA-2018:2405 | Third Party Advisory |
https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209%40%3Cdev.ignite.apache.org%3E |
Configurations
History
07 Nov 2023, 02:55
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2018-04-02 17:29
Updated : 2024-02-28 16:25
NVD link : CVE-2018-1295
Mitre link : CVE-2018-1295
CVE.ORG link : CVE-2018-1295
JSON object : View
Products Affected
apache
- ignite
CWE
CWE-502
Deserialization of Untrusted Data