CVE-2018-1295
Last modified
CVE-2018-1295 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 6.71% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Ignite | <= 2.3.0 |
References
- http://www.securityfocus.com/bid/103692Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2018:2405Third Party Advisory
- http://www.securityfocus.com/bid/103692Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2018:2405Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-1295?
How severe is CVE-2018-1295?
How do I fix CVE-2018-1295?
Are you affected by CVE-2018-1295?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
