# CVE-2018-1295: Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization

> Attackers can execute arbitrary code by sending malicious serialized objects to Apache Ignite endpoints due to missing class whitelisting.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-chp4-rv79-68j3

## What is CVE-2018-1295?

CVE-2018-1295 is a critical unsafe deserialization vulnerability in Apache Ignite, published on 2 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2018-1295?

2 open source packages ship an affected version, including org.apache.ignite:ignite-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.ignite:ignite-core` | Maven | All versions | 2.4 |
| `org.apache.ignite:ignite-core` | Maven | All versions | 2.4 |

Products: Apache Ignite.

## How do I fix CVE-2018-1295?

Upgrade org.apache.ignite:ignite-core to 2.4 or later.

## Is CVE-2018-1295 being exploited?

There is no known exploitation of CVE-2018-1295 in the wild and no public exploit code.

## Other vulnerabilities in Apache Ignite

- [CVE-2018-1273](https://insights.sbomify.com/CVE-2018-1273/): VMware Tanzu Spring Data Commons Property Binder (critical 9.8, exploited in the wild)
- [CVE-2018-8018](https://insights.sbomify.com/CVE-2018-8018/): Code execution via deserialization in org.apache.ignite:ignite-core (critical 9.8)
- [CVE-2024-52577](https://insights.sbomify.com/CVE-2024-52577/): Apache Ignite: Possible RCE when deserializing incoming messages by the server node (critical 9.5)
- [CVE-2020-1963](https://insights.sbomify.com/CVE-2020-1963/): File system access via H2 in Apache Ignite (critical 9.1)
- [CVE-2025-48977](https://insights.sbomify.com/CVE-2025-48977/): Apache Ignite: REST HTTP arbitrary file read vulnerability (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1295 and fix it if it is affected.

What it is: CVE-2018-1295 is a critical unsafe deserialization vulnerability in Apache Ignite, published on 2 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1295 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.ignite:ignite-core (Maven): affected all versions; fixed in 2.4
- org.apache.ignite:ignite-core (Maven): affected all versions; fixed in 2.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1295/ (Markdown: https://insights.sbomify.com/CVE-2018-1295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1295
- OSV: https://osv.dev/vulnerability/CVE-2018-1295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1295/
Summaries are generated and may contain mistakes; the official description above is the record.