apache/ignite · Security
Apache Ignite: Possible RCE when deserializing incoming messages by the server node
- GHSA ID
- GHSA-8355-xj3p-hv6q
- CVE ID
- CVE-2024-52577
- Severity
- critical
- Published
- Updated
- CVSS
- 9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
- CVSS v3
- 9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
- CVSS v4
- 9.5 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description
In Apache Ignite versions from 2.6.0 and before 2.17.0, configured Class Serialization Filters are ignored for some Ignite endpoints. The vulnerability could be exploited if an attacker manually crafts an Ignite message containing a vulnerable object whose class is present in the Ignite server classpath and sends it to Ignite server endpoints. Deserialization of such a message by the Ignite server may result in the execution of arbitrary code on the Apache Ignite server side.
CWEs
- CWE-502 · Deserialization of Untrusted Data
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-52577 ↗
- https://lists.apache.org/thread/1bst0n27m9kb3b6f6hvlghn182vqb2hh ↗
- https://github.com/apache/ignite/commit/f1d3579eabb2c6f5b11b94d58600afc497a8603d ↗
- http://www.openwall.com/lists/oss-security/2025/02/14/2 ↗
- https://github.com/advisories/GHSA-8355-xj3p-hv6q ↗