Description
In Apache Qpid Broker-J 0.18 through 0.32, if the broker is configured with different authentication providers on different ports one of which is an HTTP port, then the broker can be tricked by a remote unauthenticated attacker connecting to the HTTP port into using an authentication provider that was configured on a different port. The attacker still needs valid credentials with the authentication provider on the spoofed port. This becomes an issue when the spoofed port has weaker authentication protection (e.g., anonymous access, default accounts) and is normally protected by firewall rules or similar which can be circumvented by this vulnerability. AMQP ports are not affected. Versions 6.0.0 and newer are not affected.
Remediation
References
https://qpid.apache.org/cves/CVE-2017-15702.html
https://issues.apache.org/jira/browse/QPID-8039
http://www.securityfocus.com/bid/102040
https://lists.apache.org/thread.html/59d241e30db23b8b0af26bb273f789aa1f08515d3dc1a3868d3ba090%40%3Cdev.qpid.apache.org%3E
Related Vulnerabilities
CVE-2018-1999037 Vulnerability in maven package org.jenkins-ci.plugins:resource-disposer
CVE-2013-5855 Vulnerability in maven package com.sun.faces:jsf-impl
CVE-2014-0364 Vulnerability in maven package org.igniterealtime.smack:smack
CVE-2022-31147 Vulnerability in maven package org.webjars.npm:jquery-validation
CVE-2022-3971 Vulnerability in npm package matrix-appservice-irc