9.8crit

CVE-2018-1295

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

Also known as GHSA-chp4-rv79-68j3

Published 8 y ago · modified 4 mo ago · JSON

CVSS
9.8
v3.0 · NVD
CISA KEV
No
not known exploited
EPSS
6.3%
percentile 94%
Public exploits
0
none known

Summary

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.

Exploit prediction (EPSS)

6.35% probability of exploitation in the next 30 days, higher than 94% of all scored CVEs.

CVSS scores

Assigned byVersionScoreVector
NVD3.09.8CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD2.07.5AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub3.09.8CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

EcosystemPackageAffectedFixed in
mavenorg.apache.ignite:ignite-core
<2.4
2.4

Affected products

  • Apache Software Foundation Apache Ignite

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

  • lists.apache.org /thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209%40%3Cdev.ignite.apac · mailing-list, x_refsource_MLIST, x_transferred
  • access.redhat.com /errata/RHSA-2018:2405 · vendor-advisory, x_refsource_REDHAT, x_transferred
  • securityfocus.com /bid/103692 · vdb-entry, x_refsource_BID, x_transferred
  • nvd.nist.gov /vuln/detail/CVE-2018-1295 · advisory
  • github.com /advisories/GHSA-chp4-rv79-68j3 · advisory
  • github.com /apache/ignite · package
  • lists.apache.org /thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209@%3Cdev.ignite.apache · web
  • web.archive.org /web/20200227125559/http://www.securityfocus.com/bid/103692 · web

Sources

vulnwire keeps one entry per vulnerability: the CVE id wins, then GHSA; records that alias each other are merged. Machine-readable: JSON.