CVE-2018-1295

ignite: Possible Execution of Arbitrary Code Within Deserialization Endpoints

Published Apr 2, 2018 CVSS 3.0 · 9.8 Critical EPSS 6.3% KEV · Not listed
Description
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.

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-0580 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.
Github GHSA Github GHSA GHSA-chp4-rv79-68j3 Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 17, 2024, 1:06 AM
Reserved
Dec 7, 2017, 12:00 AM
Status
Modified
Published
Apr 2, 2018, 5:29 PM
Modified
Jun 17, 2026, 1:50 AM
Severity
Important
Public date
Apr 2, 2018, 12:00 AM