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-2020-7624 Vulnerability in npm package effect
CVE-2023-26486 Vulnerability in npm package vega-functions
CVE-2020-2298 Vulnerability in maven package org.jenkins-ci.plugins:nerrvana-plugin
CVE-2018-19056 Vulnerability in maven package org.webjars.bowergithub.pandao:editor.md
CVE-2019-17573 Vulnerability in maven package org.apache.cxf:cxf-rt-transports-http