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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (6.35%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.0
- 9.8 CRITICALCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 6.35% probability · 93th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-502
- Affected
- apache/ignite
- Source
- security@apache.org
References
- http://www.securityfocus.com/bid/103692Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2018:2405Third Party Advisory
- https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209%40%3Cdev.ignite.apache.org%3E
- http://www.securityfocus.com/bid/103692Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2018:2405Third Party Advisory
- https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209%40%3Cdev.ignite.apache.org%3E
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.