CVE-2018-8018

ignite: Improper deserialization allows for code execution via GridClientJdkMarshaller endpoint

Published Jul 19, 2018 CVSS 3.0 · 9.8 Critical EPSS 6.7% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD 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 Github GHSA GHSA-qcjv-wfcg-mmpr Code execution via deserialization in org.apache.ignite:ignite-core
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 17, 2024, 4:24 AM
Reserved
Mar 9, 2018, 12:00 AM
Status
Modified
Published
Jul 20, 2018, 1:29 AM
Modified
Jun 17, 2026, 2:04 AM
Severity
Important
Public date
Jul 19, 2018, 12:00 AM