First published: Mon Apr 02 2018(Updated: )
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.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Ignite | <=2.3.0 | |
redhat/ignite | <2.4 | 2.4 |
maven/org.apache.ignite:ignite-core | <2.4 | 2.4 |
<=2.3.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2018-1295 is critical with a severity value of 9.8.
The vulnerability in Apache Ignite 2.3 or earlier allows running arbitrary code when vulnerable classes are present in Ignite classpath.
Apache Ignite versions up to and including 2.3.0 are affected by CVE-2018-1295.
To fix the vulnerability, upgrade Apache Ignite to version 2.4 or later.
More information about CVE-2018-1295 can be found at the following references: [Link 1](https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209@%3Cdev.ignite.apache.org%3E), [Link 2](https://access.redhat.com/errata/RHSA-2018:2405), [Link 3](https://bugzilla.redhat.com/show_bug.cgi?id=1563133).