ignite: Improper deserialization allows for code execution via GridClientJdkMarshaller endpoint
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Ignite | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Fuse 7.2 | |||
| camel-ignite | cpe:/a:redhat:jboss_fuse:7 | RHSA-2018:3768 | 2018-12-04T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-0661 | 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 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. |
Github GHSA |
GHSA-qcjv-wfcg-mmpr | Code execution via deserialization in org.apache.ignite:ignite-core |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 6.7% (6.705% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.