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.
References
Link | Resource |
---|---|
http://www.securityfocus.com/bid/103692 | Third Party Advisory VDB Entry |
https://access.redhat.com/errata/RHSA-2018:2405 | Third Party Advisory |
https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209%40%3Cdev.ignite.apache.org%3E |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: apache
Published: 2018-04-01T00:00:00
Updated: 2018-08-15T09:57:01
Reserved: 2017-12-07T00:00:00
Link: CVE-2018-1295
JSON object: View
NVD Information
Status : Modified
Published: 2018-04-02T17:29:00.277
Modified: 2023-11-07T02:55:55.760
Link: CVE-2018-1295
JSON object: View
Redhat Information
No data.
CWE