The camel-irc producer chooses the destination of an outgoing IRC message from the irc.sendTo Exchange header (the constant IrcConstants.IRC_SEND_TO, value irc.sendTo); when that header is present it overrides the channel list configured on the endpoint, and the message is sent only to the specified destination. This and the component's other control headers (irc.target, irc.messageType, irc.user.*, irc.num, irc.value) used plain, non-Camel-prefixed values. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks only the Camel header namespace on the HTTP boundary - let them pass from an inbound HTTP request straight into the Exchange. In a route that bridges an HTTP consumer (for example platform-http) into an irc: producer, any HTTP client could therefore set the irc.sendTo header and redirect a message that the route intended for a configured channel to an arbitrary IRC channel or user - exfiltrating the message content to an attacker-chosen nickname, leaking it into a public channel, or delivering messages that appear to come from the bot. No credentials are required when the bridging consumer is unauthenticated.
This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.
Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, routes that set IRC headers via the raw header names must use the CamelIrc* names (for example CamelIrcSendTo) instead of the old irc.* values. For deployments that cannot upgrade immediately, strip the irc.* headers from any untrusted ingress before the irc: producer (for example removeHeaders('irc.*') at the start of the route), and set the IRC destination from a trusted source.
Summary
AIThe Apache Camel IRC producer can accept an untrusted irc.sendTo header that overrides its configured message destination. In a route bridging an HTTP consumer to an IRC producer, a remote client can redirect messages to an attacker-chosen IRC channel or user; no credentials are needed if the HTTP consumer is unauthenticated, and no user interaction is required.
Who should check
Check deployments using Maven org.apache.camel:camel-irc versions 4.0.0–before 4.14.8, 4.15.0–before 4.18.3, or 4.19.0–before 4.21.0, especially routes bridging HTTP consumers to IRC producers.
What to do
- 1Upgrade to 4.21.0, or to 4.14.8 or 4.18.3 on those respective release streams.
- 2After upgrading, replace raw irc.* control header names with CamelIrc* names.
- 3If you cannot upgrade immediately, strip irc.* headers at untrusted ingress before the IRC producer and set the destination from a trusted source.