First published: Thu Jul 19 2018(Updated: )
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.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Ignite | <2.4.8 | |
Apache Ignite | >2.5.0<2.5.3 | |
redhat/ignite | <2.6 | 2.6 |
maven/org.apache.ignite:ignite-core | <2.6 | 2.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2018-8018 is critical with a CVSS score of 9.8.
CVE-2018-8018 affects Apache Ignite versions before 2.4.8 and 2.5.x before 2.5.3.
The vulnerability in CVE-2018-8018 is a serialization mechanism that does not have a list of allowed classes, allowing for arbitrary code execution.
Yes, the vulnerability in CVE-2018-8018 can be exploited remotely.
To fix CVE-2018-8018, upgrade to Apache Ignite version 2.6 or above.