CVE-2026-33453

Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Apache Camel Camel-Coap component. Apache Camel's camel-coap component is vulnerable to Camel message header injection, leading to remote code execution when routes forward CoAP requests to header-sensitive producers (e.g. camel-exec) The camel-coap component maps incoming CoAP request URI query parameters directly into Camel Exchange In message headers without applying any HeaderFilterStrategy.   Specifically, CamelCoapResource.handleRequest() iterates over OptionSet.getUriQuery() and calls camelExchange.getIn().setHeader(...) for every query parameter. CoAPEndpoint extends DefaultEndpoint rather than DefaultHeaderFilterStrategyEndpoint, and CoAPComponent does not implement HeaderFilterStrategyComponent; the component contains no references to HeaderFilterStrategy at all. As a result, an unauthenticated attacker who can send a single CoAP UDP packet to a Camel route consuming from coap:// can inject arbitrary Camel internal headers (those prefixed with Camel*) into the Exchange. When the route delivers the message to a header-sensitive producer such as camel-exec, camel-sql, camel-bean, camel-file, or template components (camel-freemarker, camel-velocity), the injected headers can alter the producer's behavior. In the case of camel-exec, the CamelExecCommandExecutable and CamelExecCommandArgs headers override the executable and arguments configured on the endpoint, resulting in arbitrary OS command execution under the privileges of the Camel process. The producer's output is written back to the Exchange body and returned in the CoAP response payload by CamelCoapResource, giving the attacker an interactive RCE channel without any need for out-of-band exfiltration.                                                                                                                                                                         Exploitation prerequisites are minimal: a single unauthenticated UDP datagram to the CoAP port (default 5683). CoAP (RFC 7252) has no built-in authentication, and DTLS is optional and disabled by default. Because the protocol is UDP-based, HTTP-layer WAF/IDS controls do not apply. This issue affects Apache Camel: from 4.14.0 through 4.14.5, from 4.18.0 before 4.18.1, 4.19.0. Users are recommended to upgrade to version 4.18.1 or 4.19.0, fixing the issue.

Apache Camel's camel-coap component is vulnerable to header injection because it maps CoAP request URI query parameters directly into Camel message headers without applying a HeaderFilterStrategy. An unauthenticated attacker can send a crafted CoAP request to inject arbitrary Camel internal headers into the exchange. When a vulnerable route forwards that exchange to a header-sensitive downstream producer, the attacker may be able to control producer behavior. For example, in routes using camel-exec, injected headers can override the configured executable and arguments, which can result in arbitrary command execution with the privileges of the Camel process. Command output may be returned to the attacker in the CoAP response. This issue affects org.apache.camel:camel-coap from 4.14.0 through 4.14.5 and from 4.18.0 before 4.18.1. It is fixed in 4.14.6, 4.18.1, and 4.19.0.

Apache Camel's camel-coap component is vulnerable to header injection because it maps CoAP request URI query parameters directly into Camel message headers without applying a HeaderFilterStrategy. An unauthenticated attacker can send a crafted CoAP request to inject arbitrary Camel internal headers into the exchange. When a vulnerable route forwards that exchange to a header-sensitive downstream producer, the attacker may be able to control producer behavior. For example, in routes using camel-exec, injected headers can override the configured executable and arguments, which can result in arbitrary command execution with the privileges of the Camel process. Command output may be returned to the attacker in the CoAP response. This issue affects org.apache.camel:camel-coap from 4.14.0 through 4.14.5 and from 4.18.0 before 4.18.1. It is fixed in 4.14.6, 4.18.1, and 4.19.0.

Vulnerabilidad de Modificación Incontrolada de Atributos de Objeto Determinados Dinámicamente en el componente Camel-Coap de Apache Camel. El componente camel-coap de Apache Camel es vulnerable a la inyección de encabezados de mensajes de Camel, lo que lleva a la ejecución remota de código cuando las rutas reenvían solicitudes CoAP a productores sensibles a encabezados (p. ej., camel-exec). El componente camel-coap mapea los parámetros de consulta URI de las solicitudes CoAP entrantes directamente en los encabezados de mensajes de entrada de Camel Exchange sin aplicar ninguna HeaderFilterStrategy. Específicamente, CamelCoapResource.handleRequest() itera sobre OptionSet.getUriQuery() y llama a camelExchange.getIn().setHeader(...) para cada parámetro de consulta. CoAPEndpoint extiende DefaultEndpoint en lugar de DefaultHeaderFilterStrategyEndpoint, y CoAPComponent no implementa HeaderFilterStrategyComponent; el componente no contiene ninguna referencia a HeaderFilterStrategy en absoluto. Como resultado, un atacante no autenticado que puede enviar un único paquete UDP CoAP a una ruta Camel que consume de coap:// puede inyectar encabezados internos arbitrarios de Camel (aquellos prefijados con Camel) en el Exchange. Cuando la ruta entrega el mensaje a un productor sensible a encabezados como camel-exec, camel-sql, camel-bean, camel-file, o componentes de plantilla (camel-freemarker, camel-velocity), los encabezados inyectados pueden alterar el comportamiento del productor. En el caso de camel-exec, los encabezados CamelExecCommandExecutable y CamelExecCommandArgs anulan el ejecutable y los argumentos configurados en el endpoint, lo que resulta en la ejecución arbitraria de comandos del sistema operativo bajo los privilegios del proceso Camel. La salida del productor se escribe de nuevo en el cuerpo del Exchange y es devuelta en la carga útil de la respuesta CoAP por CamelCoapResource, dando al atacante un canal RCE interactivo sin necesidad de exfiltración fuera de banda. Los requisitos previos para la explotación son mínimos: un único datagrama UDP no autenticado al puerto CoAP (predeterminado 5683). CoAP (RFC 7252) no tiene autenticación incorporada, y DTLS es opcional y está deshabilitado por defecto. Debido a que el protocolo es basado en UDP, los controles WAF/IDS de capa HTTP no se aplican. Este problema afecta a Apache Camel: desde 4.14.0 hasta 4.14.5, desde 4.18.0 antes de 4.18.1, 4.19.0. Se recomienda a los usuarios actualizar a la versión 4.18.1 o 4.19.0, solucionando el problema.