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 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 GridClientJdkMarshaller deserialization endpoint.

Affected: Maven: org.apache.ignite:ignite-core

Apache Ignite 2.5 and earlier 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 GridClientJdkMarshaller deserialization endpoint.

xmlrpc: XML external entity vulnerability SSRF via a crafted DTD xmlrpc: Deserialization of untrusted Java object through <ex:serializable> tag undertow: Client can use bogus uri in Digest authentication spring-framework: ReDoS Attack with spring-messaging spring-data-commons: XXE with Spring Data’s XMLBeam integration kafka: Users can perform Broker actions via crafted fetch requests, interfering with data replication and causing data lass tomcat: A bug in the UTF-8 decoder can lead to DoS tomcat: Insecure defaults in CORS filter enable 'supportsCredentials' for all origins ignite: Improper deserialization allows for code execution via GridClientJdkMarshaller endpoint apache-cxf: TLS hostname verification does not work correctly with com.sun.net.ssl.* camel-mail: path traversal vulnerability vertx: Improper neutralization of CRLF sequences allows remote attackers to inject arbitrary HTTP response headers