{"id":"CVE-2018-1295","aliases":["EUVD-2018-0580","GHSA-chp4-rv79-68j3"],"status":"published","title":"Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization","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.","severity":{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.06349,"percentile":0.93688,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-502"],"published":"2018-04-02T17:00:00Z","modified":"2026-10-24T10:30:19Z","fixes":[{"ecosystem":"Maven","package":"org.apache.ignite:ignite-core","fixed_in":["2.4"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.apache.ignite:ignite-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4"}]}]},{"source":"osv","ecosystem":"Maven","package":"org.apache.ignite:ignite-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4"}]}],"versions":["1.0.0","1.0.0-RC1","1.0.0-RC3","1.1.0-incubating","1.2.0-incubating","1.3.0-incubating","1.4.0","1.5.0-b1","1.5.0.final","1.6.0","1.7.0","1.8.0","1.9.0","2.0.0","2.1.0","2.2.0","2.3.0"]}],"products":[{"vendor":"apache","product":"ignite"},{"vendor":"apache software foundation","product":"apache ignite"}],"references":[{"url":"https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209%40%3Cdev.ignite.apache.org%3E","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"https://access.redhat.com/errata/RHSA-2018:2405","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory","web"]},{"url":"http://www.securityfocus.com/bid/103692","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1295","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-chp4-rv79-68j3","tags":["advisory"]},{"url":"https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209@%3Cdev.ignite.apache.org%3E","tags":["web"]},{"url":"https://web.archive.org/web/20200227125559/http://www.securityfocus.com/bid/103692","tags":["web"]},{"url":"https://github.com/apache/ignite","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2018-1295","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.","status":"published","published":"2018-04-02T17:00:00Z","modified":"2024-09-17T01:06:48.932Z","updated_at":"2026-11-02T14:35:09.139955Z"}],"euvd":[{"id":"EUVD-2018-0580","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.","status":"published","published":"2018-04-02T17:00:00Z","modified":"2024-09-17T01:06:48Z","updated_at":"2026-11-03T00:28:52.69419Z"}],"ghsa":[{"id":"GHSA-chp4-rv79-68j3","title":"Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization","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.","status":"published","published":"2018-10-16T20:53:44Z","modified":"2024-04-19T19:24:02Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-502"],"updated_at":"2026-11-02T14:37:43.62603Z"}],"nvd":[{"id":"CVE-2018-1295","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.","status":"published","published":"2018-04-02T17:29:00.277Z","modified":"2026-06-17T01:50:56.513Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary"},{"version":"2.0","score":7.5,"vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","level":"high","assessor":"primary"}],"cwes":["CWE-502"],"updated_at":"2026-11-02T14:04:24.700429Z"}],"osv":[{"id":"CVE-2018-1295","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.","status":"published","published":"2018-04-02T17:29:00.277Z","modified":"2026-10-24T10:30:19.636779838Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:44:07.934182Z"},{"id":"GHSA-chp4-rv79-68j3","title":"Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization","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.","status":"published","published":"2018-10-16T20:53:44Z","modified":"2024-04-19T19:31:30.688152Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-502"],"updated_at":"2026-11-02T15:46:45.28161Z"}]}}
