First published: Fri Feb 14 2025(Updated: )
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.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Ignite | >=2.6.0<2.17.0 | |
maven/org.apache.ignite:ignite-core | >=2.6.0<2.17.0 | 2.17.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-52577 is considered to be a high-severity vulnerability due to its potential for exploitation through crafted Ignite messages.
To fix CVE-2024-52577, upgrade Apache Ignite to a version later than 2.17.0.
CVE-2024-52577 affects Apache Ignite versions from 2.6.0 up to, but not including, 2.17.0.
An attacker can exploit CVE-2024-52577 by crafting Ignite messages that include vulnerable objects, potentially leading to remote code execution.
Currently, the best mitigation for CVE-2024-52577 is to update to a non-vulnerable version of Apache Ignite.