CVE-2018-1295: Critical severity Apache Ignite vulnerability

Published Apr 2, 2018
·
Updated

Apache Ignite 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.

External References:

https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209@%3Cdev.ignite.apache.org%3E

Other sources

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.

Affected Software

3 affected componentsFixes available
Apache Ignite<=2.3.0
redhat/ignite<2.4
2.4
maven/org.apache.ignite:ignite-core<2.4
2.4

Event History

Apr 2, 2018
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
DescriptionWeakness
Apr 3, 2018
Data Sourced
via Red Hat·08:51 AM
DescriptionSeverityAffected Software
Oct 16, 2018
Advisory Published
via GitHub·08:53 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2018-1295?

The severity of CVE-2018-1295 is critical with a severity value of 9.8.

2

How does Apache Ignite 2.3 or earlier serialization mechanism vulnerability work?

The vulnerability in Apache Ignite 2.3 or earlier allows running arbitrary code when vulnerable classes are present in Ignite classpath.

3

What software versions are affected by CVE-2018-1295?

Apache Ignite versions up to and including 2.3.0 are affected by CVE-2018-1295.

4

How can I fix the CVE-2018-1295 vulnerability?

To fix the vulnerability, upgrade Apache Ignite to version 2.4 or later.

5

Where can I find more information about CVE-2018-1295?

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).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203