Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.2.3, 3.3.1
-
None
Description
SecuredBroker checks security AFTER a component is invoked, which works fine when the consumer and components are on the same broker. If a consumer is on brokerA and a provider endpoint is on brokerB using JMSFlow it is possible to bypass security and invoke the endpoint on brokerB even if it is using SecuredBroker.