CVE-2018-1295
CRITICAL9.8EPSS 5.6%Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization
Published: 10/16/2018Modified: 4/19/2024
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.
Affected packages (1)
- Maven/org.apache.ignite:ignite-corefrom 0, < 2.4
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 3.1 | CRITICAL9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
References (6)
- ADVISORYhttps://github.com/advisories/GHSA-chp4-rv79-68j3
- ADVISORYhttps://nvd.nist.gov/vuln/detail/CVE-2018-1295
- PATCHhttps://github.com/apache/ignite
- WEBhttps://access.redhat.com/errata/RHSA-2018:2405
- WEBhttps://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209@%3Cdev.ignite.apache.org%3E
- WEBhttps://web.archive.org/web/20200227125559/http://www.securityfocus.com/bid/103692