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.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HApache Ignite
APPApache≤ 2.3.0
Related vulnerabilities
RCE w Spring Data Commons — podatność property bindera
Apache Ignite: pominięcie filtrów deserializacji umożliwia RCE
Apache Ignite — nieautoryzowany dostęp do systemu plików przez funkcje SQL H2
Apache Ignite: RCE przez niebezpieczną deserializację obiektów Java
Relative Path Traversal vulnerability in Apache Ignite REST API. Authenticated REST API users can read any fi...