Vulnerability Description
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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apache | Ignite | <= 2.3.0 |
Related Weaknesses (CWE)
References
- http://www.securityfocus.com/bid/103692Third Party AdvisoryVDB Entry
- https://access.redhat.com/errata/RHSA-2018:2405Third Party Advisory
- https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5
- http://www.securityfocus.com/bid/103692Third Party AdvisoryVDB Entry
- https://access.redhat.com/errata/RHSA-2018:2405Third Party Advisory
- https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5
FAQ
What is CVE-2018-1295?
CVE-2018-1295 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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 vu...
How severe is CVE-2018-1295?
CVE-2018-1295 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2018-1295?
Check the references section above for vendor advisories and patch information. Affected products include: Apache Ignite.