CVE-2017-15702
CriticalSummary
In Apache Qpid Broker-J versions 0.18 through 0.32, misconfiguration of ports with different authentication providers can allow a remote attacker connecting to the HTTP port to trick the broker into using an authentication provider from another port. The attacker must have valid credentials for the provider on the spoofed port.
Risk Assessment
The risk to the organization is that an attacker could gain access to the system by exploiting weaker authentication mechanisms, potentially leading to unauthorized access to resources. This threat is particularly significant when ports are protected by firewall rules.
Recommendation
It is recommended that administrators ensure proper configuration and security of ports with different authentication providers, and avoid using weaker authentication mechanisms on ports that may be externally accessible.
Original NVD description (English source)
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.