Code execution via deserialization in org.apache.ignite:ignite-core
Apache Ignite 2.5 and earlier 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 GridClientJdkMarshaller deserialization endpoint.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-8018US | critical9.8 | — | ||
In Apache Ignite before 2.4.8 and 2.5.x before 2.5.3, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2018:3768WEB
- https://github.com/advisories/GHSA-qcjv-wfcg-mmprADVISORY
- https://github.com/apache/ignite/commit/82a7b8209fcf56971d12cb10410a38ed632215bWEB
- https://issues.apache.org/jira/browse/IGNITE-8565WEB
- https://lists.apache.org/thread.html/e0fdf53114a321142ecfa5cfa17658090f0b4e1677de431e329b37ab@%3Cdev.ignite.apache.org%3EWEB
- https://nvd.nist.gov/vuln/detail/CVE-2018-8018ADVISORY
scry
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