kali834x opened a new pull request, #1339:
URL: https://github.com/apache/axis-axis2-java-core/pull/1339

   JMSTargetAddressPolicy.rejectionReason now also refuses a remote JNDI scheme 
in transport.jms.ConnectionFactoryJNDIName. JMSSender.sendMessage runs the 
policy on every JMS target address, including a decoupled wsa:ReplyTo when jms 
is among allowedResponseEndpointSchemes, but it only checked the destination 
name, transport.jms.ReplyDestination and java.naming.provider.url. 
JMSOutTransportInfo.createJMSSender looks the connection factory name up with 
InitialContext.lookup whenever the sender has no configured factory for the 
address, and the address can force that by naming an unknown 
transport.jms.ConnectionFactory, so 
jms:/Queue?transport.jms.ConnectionFactory=none&transport.jms.ConnectionFactoryJNDIName=ldap://host/x
 is resolved through the ldap URL context factory against the caller's 
directory (JNDI injection, CWE-917). the AXIS2-6062 substring guard that 2.0.2 
replaced searched the whole address and caught this; the field-by-field 
replacement listed three of the four names an 
 address resolves. ordinary factory names are unaffected. a scratch run with 
ActiveMQ's initial context factory and a local listener showed the policy 
accepting the address and createJMSSender connecting to the listener before, 
and the address refused with no connection after. JMSTargetAddressPolicyTest 
gains a case that fails before the change; the jms module (158 tests) passes 
with -Papache-release.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to