The camel-dapr Dapr Pub/Sub consumer (DaprPubSubConsumer) copied two fields from each inbound CloudEvent - its Pub/Sub component name and its topic - into the CamelDaprPubSubName and CamelDaprTopic Exchange headers. These two headers are producer-direction routing headers: when the route republishes through a Dapr producer, DaprConfigurationOptionsProxy reads them back and prefers them over the destination configured on the endpoint. As a result, in a route that consumes from one Dapr Pub/Sub topic and republishes to another (for example from('dapr-pubsub:p:t').to('dapr-pubsub:p:other')), an actor able to publish a message to the subscribed topic could set the CloudEvent's pub/sub-name and topic to values of their choosing and cause the re-published message to be delivered to an arbitrary Dapr Pub/Sub component and topic instead of the configured destination - redirecting or exfiltrating the message and bypassing the route's intended routing and any topic-level access controls in the underlying broker. Exploitation requires the ability to publish to the topic the route subscribes to; no other authentication or user interaction is needed.
This issue affects Apache Camel: from 4.12.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. For deployments that cannot upgrade immediately, remove the CamelDaprPubSubName and CamelDaprTopic headers from the Exchange between the Dapr consumer and any Dapr producer in the route (for example removeHeaders('CamelDaprPubSubName', 'CamelDaprTopic')), and restrict who can publish to the subscribed Dapr Pub/Sub topic so that only trusted producers can send to it.
Summary
AIThe Apache Camel Dapr Pub/Sub consumer copies inbound CloudEvent values into routing headers that a Dapr producer can use instead of its configured destination. In a route that consumes and republishes messages, an actor able to publish to the subscribed topic can redirect republished messages to a Dapr Pub/Sub component and topic of their choosing. No other authentication or user interaction is needed.
Who should check
Check deployments using org.apache.camel:camel-dapr versions 4.12.0 to before 4.14.8, 4.15.0 to before 4.18.3, or 4.19.0 to before 4.21.0.
What to do
- 1Upgrade to 4.14.8 on the 4.14.x LTS stream, 4.18.3 on the 4.18.x stream, or 4.21.0.
- 2If you cannot upgrade immediately, remove the CamelDaprPubSubName and CamelDaprTopic headers between the Dapr consumer and any Dapr producer in the route.
- 3Restrict publishing to the subscribed Dapr Pub/Sub topic to trusted producers.