Skip to content
Fencer Intel
critical 9.8

CVE-2018-8018 json

Code execution via deserialization in org.apache.ignite:ignite-core

published 8y ago modified 4mo ago also GHSA-qcjv-wfcg-mmpr , EUVD-2018-0661

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.7%
EPSS 6.7% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

In Apache Ignite before 2.4.8 and 2.5.x before 2.5.3, 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 GridClientJdkMarshaller deserialization endpoint.

Patch / fix

  • maven org.apache.ignite:ignite-core 2.6
  • apache ignite 2.4.8, 2.5.3

Is CVE-2018-8018 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-8018 updated cvss 8.1

ignite: Improper deserialization allows for code execution via GridClientJdkMarshaller endpoint

  • Red Hat JBoss Fuse 6 camel-ignite camel-ignite
    affected: no fix available
  • Red Hat Fuse 7.2
    fixed: vendor fix RHSA-2018:3768

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.71% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.ignite:ignite-core
<2.6
2.6

Affected products

  • Apache Software Foundation Apache Ignite

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.