GitHub Advisoryadvisory · Maven

GHSA-chp4-rv79-68j3 Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization

CRITICAL Published 2018-10-16 Modified 2024-04-19 Official page ↗
Aliases
CVE-2018-1295
Ecosystem
Maven
Packages
org.apache.ignite:ignite-core
Severity
Critical
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-502
Reviewed
2020-06-16

Affected packages

• Maven org.apache.ignite:ignite-core: < 2.4 → fixed in 2.4

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.

Related

Alias · CVE (1)

  • CVE-2018-1295 In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization,… vulnerability

Weakness · CWE (1)

  • CWE-502 Deserialization of Untrusted Data weakness

References