CVE-2018-8018: Critical severity Apache Ignite vulnerability
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.
Other sources
Apache Ignite through version 2.5's 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.
External References:
https://lists.apache.org/thread.html/e0fdf53114a321142ecfa5cfa17658090f0b4e1677de431e329b37ab@%3Cdev.ignite.apache.org%3E
— Red Hat
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 Software
Event History
Frequently Asked Questions
What is the severity of CVE-2018-8018?
The severity of CVE-2018-8018 is critical with a CVSS score of 9.8.
How does CVE-2018-8018 affect Apache Ignite?
CVE-2018-8018 affects Apache Ignite versions before 2.4.8 and 2.5.x before 2.5.3.
What is the vulnerability in CVE-2018-8018?
The vulnerability in CVE-2018-8018 is a serialization mechanism that does not have a list of allowed classes, allowing for arbitrary code execution.
Can the vulnerability in CVE-2018-8018 be exploited remotely?
Yes, the vulnerability in CVE-2018-8018 can be exploited remotely.
How can I fix CVE-2018-8018?
To fix CVE-2018-8018, upgrade to Apache Ignite version 2.6 or above.