CVE-2018-1295 json
Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization
published 2018-04-02 8 y ago modified 2026-06-17 4 mo ago also GHSA-chp4-rv79-68j3 , EUVD-2018-0580
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.3%
- EPSS 6.3% chance of exploitation in 30 days, percentile 93%
- 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.
Patch / fix
- maven org.apache.ignite:ignite-core 2.4
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-1295 updated cvss 8.1
ignite: Possible Execution of Arbitrary Code Within Deserialization Endpoints
-
Red Hat Fuse 7 camel Red Hat JBoss Fuse 6 camel Red Hat JBoss Fuse Integration Service 2 ignite-core ignite-coreaffected: no fix available
-
Red Hat Fuse Intergration Services 2.0 based on Fuse 6.3 R7fixed: vendor fix RHSA-2018:2405
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.35% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
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.4 |
2.4 |
Affected products
- Apache Software Foundation Apache Ignite
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
access.redhat.com
/errata/RHSA-2018:2405
vendor-advisory, web, third-party-advisory
-
lists.apache.org
/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209%40%3Cdev.ignite.apache.org%3E
mailing-list
-
securityfocus.com
/bid/103692
vdb-entry, third-party-advisory
-
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.org%3E
web
-
web.archive.org
/web/20200227125559/http://www.securityfocus.com/bid/103692
web
Sources
- CVE List CVE-2018-1295
- GitHub Advisory GHSA-chp4-rv79-68j3
- NVD CVE-2018-1295
Fencer Vulns 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.