Описание
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.
A flaw was found in Apache Ignite. This vulnerability allows remote code execution via specially crafted Ignite messages that bypass Class Serialization Filters.
Отчет
No Red Hat products are affected by this vulnerability. This vulnerability marked as Important severity rather than Critical because, while it allows remote code execution (RCE), it requires specific conditions to be met for successful exploitation. An attacker must craft a malicious Ignite message containing a deserializable object that is already present in the server’s classpath, which limits the attack surface compared to unauthenticated arbitrary code execution vulnerabilities. Additionally, exploitation is constrained to environments where untrusted users have network access to vulnerable Ignite endpoints.
Меры по смягчению последствий
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat build of Apache Camel for Spring Boot 4 | org.apache.ignite/ignite-core | Not affected | ||
| Red Hat Fuse 7 | org.apache.ignite/ignite-core | Not affected | ||
| Red Hat Integration Camel K 1 | org.apache.ignite/ignite-core | Not affected |
Показывать по
Дополнительная информация
Статус:
EPSS
9.8 Critical
CVSS3
Связанные уязвимости
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.
Apache Ignite: Possible RCE when deserializing incoming messages by the server node
Уязвимость распределённой база данных для высокопроизводительных вычислений Apache Ignite, связанная с недостатками механизма десериализации, позволяющая нарушителю выполнить произвольный код
EPSS
9.8 Critical
CVSS3