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.
References
Link | Resource |
---|---|
http://www.securityfocus.com/bid/104911 | Third Party Advisory VDB Entry |
https://access.redhat.com/errata/RHSA-2018:3768 | Third Party Advisory |
https://lists.apache.org/thread.html/e0fdf53114a321142ecfa5cfa17658090f0b4e1677de431e329b37ab%40%3Cdev.ignite.apache.org%3E |
Configurations
Configuration 1 (hide)
|
History
07 Nov 2023, 03:01
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2018-07-20 01:29
Updated : 2024-02-28 16:48
NVD link : CVE-2018-8018
Mitre link : CVE-2018-8018
CVE.ORG link : CVE-2018-8018
JSON object : View
Products Affected
apache
- ignite
CWE
CWE-502
Deserialization of Untrusted Data