Apache Camel: Camel Message Header Injection via Improper Filtering
Apache Software Foundation Apache Camel
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.camel:camel-support Maven |
|
|
Apache Software Foundation Apache Camel
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.camel:camel-support Maven |
|
|
Bypass/Injection vulnerability in Apache Camel components under particular conditions.
This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from 3.10.0 through <= 3.22.3.
Users are recommended to upgrade to version 4.10.2 for 4.10.x LTS, 4.8.5 for 4.8.x LTS and 3.22.4 for 3.x releases.
This vulnerability is present in Camel's default incoming header filter, that allows an attacker to include Camel specific
headers that for some Camel components can alter the behaviours such as the camel-bean component, to call another method
on the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send
the message to another queue (on the same broker) than was coded in the application. This could also be seen by using the camel-exec component
The attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are
From the CVE record · apache
Apache Camel’s default incoming header filter can let crafted Camel-specific headers through under particular conditions. An attacker who can send requests with custom headers to an internet-facing Camel HTTP application could change component behavior, such as invoking a different bean method or sending a JMS message to another queue on the same broker.
Teams running Apache Camel applications using Maven org.apache.camel:camel-support versions >=3.10.0 <3.22.4, >=4.0.0-M1 <4.8.5, or >=4.9.0 <4.10.2 should check their deployments.