Deserialization in Apache Ignite

CVE-2018-1295

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.

Vulnerability class: Insecure Deserialization

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.063 (93.6th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 94th percentile — 93.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2018-1295: held from 0.063 to 0.063.

EPSS over last 30 days · oldest: 0.063 · newest: 0.063 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2018-1295?
CVE-2018-1295 is a critical-severity vulnerability in Apache Ignite, classified under Deserialization of Untrusted Data. CVSS score: 9.8/10. Published 2018-04-02.
How severe is CVE-2018-1295?
Critical severity. CVSS v3 base score is 9.8 out of 10.
Is CVE-2018-1295 known to be exploited?
6 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.