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.
Remediation
References
http://www.securityfocus.com/bid/103692
https://access.redhat.com/errata/RHSA-2018:2405
https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209%40%3Cdev.ignite.apache.org%3E
Related Vulnerabilities
CVE-2022-25758 Vulnerability in npm package scss-tokenizer
CVE-2022-2218 Vulnerability in npm package parse-url
CVE-2017-8045 Vulnerability in maven package org.springframework.amqp:spring-amqp
CVE-2022-25873 Vulnerability in maven package org.webjars.bowergithub.vuetifyjs:vuetify
CVE-2020-15174 Vulnerability in maven package org.webjars.npm:electron