Описание
Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place. Any attacker able to place a message on the service's JMS destination can submit a malicious serialized object, leading to denial of service or, if a suitable gadget class is on the classpath, remote code execution. The fix disables ObjectMessage deserialization by default, with a configuration switch to re-enable it if needed. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.
A flaw was found in Apache CXF. The Java Message Service (JMS) transport component improperly deserializes inbound JMS ObjectMessages without type restrictions. A remote attacker can exploit this by sending a specially crafted message to the service's JMS destination. This vulnerability could lead to a denial of service or, in certain configurations, enable remote code execution on the affected system.
Отчет
This vulnerability in Apache CXF's JMS transport is rated as Important because it allows for remote code execution or denial of service if an attacker can send a specially crafted JMS ObjectMessage to a service. This is particularly relevant in Red Hat environments where Apache CXF is used in applications that process JMS messages, as the default deserialization behavior without type restrictions increases the attack surface. Exploitation requires the presence of a suitable gadget class on the classpath.
Меры по смягчению последствий
To mitigate this vulnerability, disable ObjectMessage deserialization in Apache CXF's JMS transport. This can typically be achieved through a configuration setting provided by the Apache CXF framework. Consult the Apache CXF documentation for specific instructions on how to disable ObjectMessage deserialization in your deployment. Disabling this feature may impact applications that rely on ObjectMessage for legitimate data transfer.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat build of Apache Camel for Spring Boot 4 | cxf-rt-transports-jms | Affected | ||
| Red Hat JBoss Enterprise Application Platform 7 | cxf | Affected | ||
| Red Hat JBoss Enterprise Application Platform 7 | cxf-rt-transports-jms | Affected | ||
| Red Hat JBoss Enterprise Application Platform 7 | eap74-els-openjdk11-openshift-rhel8/eap74-els-openjdk11-openshift-rhel8 | Will not fix | ||
| Red Hat JBoss Enterprise Application Platform 7 | eap74-els-openjdk17-openshift-rhel8/eap74-els-openjdk17-openshift-rhel8 | Will not fix | ||
| Red Hat JBoss Enterprise Application Platform 7 | eap74-els-openjdk8-openshift-rhel8/eap74-els-openjdk8-openshift-rhel8 | Will not fix | ||
| Red Hat JBoss Enterprise Application Platform 7 | jboss-eap-7-eap74-els-openjdk17-openshift-rhel8/jboss-eap-7-eap74-els-openjdk17-openshift-rhel8 | Will not fix | ||
| Red Hat JBoss Enterprise Application Platform 7 | jboss-eap-7-eap74-els-openjdk8-openshift-rhel8/jboss-eap-7-eap74-els-openjdk8-openshift-rhel8 | Will not fix | ||
| Red Hat JBoss Enterprise Application Platform 8 | cxf-rt-transports-jms | Affected | ||
| Red Hat JBoss Enterprise Application Platform Expansion Pack | cxf-rt-transports-jms | Affected |
Показывать по
Дополнительная информация
Статус:
EPSS
8.1 High
CVSS3
Связанные уязвимости
Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place. Any attacker able to place a message on the service's JMS destination can submit a malicious serialized object, leading to denial of service or, if a suitable gadget class is on the classpath, remote code execution. The fix disables ObjectMessage deserialization by default, with a configuration switch to re-enable it if needed. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.
Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place. Any attacker able to place a message on the service's JMS destination can submit a malicious serialized object, leading to denial of service or, if a suitable gadget class is on the classpath, remote code execution. The fix disables ObjectMessage deserialization by default, with a configuration switch to re-enable it if needed. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.
EPSS
8.1 High
CVSS3