Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-1295US | critical9.8 | — | ||
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 cod… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2018:2405WEB
- https://github.com/advisories/GHSA-chp4-rv79-68j3ADVISORY
- https://github.com/apache/ignitePACKAGE
- https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209@%3Cdev.ignite.apache.org%3EWEB
- https://nvd.nist.gov/vuln/detail/CVE-2018-1295ADVISORY
- https://web.archive.org/web/20200227125559/http://www.securityfocus.com/bid/103692WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan