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.
Published: 2018-07-19
Score: 9.8 Critical
EPSS: 4.4% Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

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.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2024-09-17T04:24:27.033Z

Reserved: 2018-03-09T00:00:00.000Z

Link: CVE-2018-8018

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2018-07-20T01:29:04.833

Modified: 2024-11-21T04:13:06.377

Link: CVE-2018-8018

cve-icon Redhat

Severity : Important

Publid Date: 2018-07-19T00:00:00Z

Links: CVE-2018-8018 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses