Back

CVE-2018-1295

CRITICAL

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.

Published: Apr 2, 2018 Modified: Jun 17, 2026
CWE-502

CVSS Metrics

CVSSv3
Attack Vector: NETWORK Attack Complexity: LOW Privileges Required: NONE User Interaction: NONE Scope: UNCHANGED Confidentiality Impact: HIGH Integrity Impact: HIGH Availability Impact: HIGH

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected Products (1)

Vendor Product Version
apache ignite *

GitHub Security Advisory GHSA-chp4-rv79-68j3

Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization

maven org.apache.ignite:ignite-core < 2.4 Fixed: 2.4

Risk Scores

CVSS Score 9.8 / 10
EPSS Score 6.47%

Top 7% most likely to be exploited

Threat Score 41.1 / 100

Data Sources

NVD EPSS GitHub