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.
Other vulnerabilities in Apache Qpid Broker-J
See all- CVE-2017-15701High
In Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclusive), the broker does not properly enforce a maximum frame size in AMQP 1.0 frames. A remote unauthenticated attacker could exploit this to cause the broker to exhaust all available memory and eventually terminate.
- CVE-2026-68080Medium
In Apache Qpid Broker-J through 10.0.1, it was not possible to govern the rate at which the broker would respond to an echo flow, enabling an authenticated attacker to cause excessive resource usage and potential denial of service. The issue is fixed in version 10.1.0.
- CVE-2026-68078Medium
In Apache Qpid Broker-J through 10.0.1, it was not possible to govern the maximum number of transfer frames per incoming delivery, enabling an authenticated attacker to cause excessive resource usage and potential denial of service.
- CVE-2026-68077Medium
An authenticated attacker can craft a disposition frame with large or illegal ranges causing excessive CPU usage due to naive range handling, leading to denial of service. This issue affects Apache Qpid Broker-J through 10.0.1.
- CVE-2026-68075Medium
An authenticated attacker could exceed the session flow control incoming window potentially leading to denial of service. This issue affects Apache Qpid Broker-J through 10.0.1.
- CVE-2026-68073High
A pre-authentication attacker could leverage type nesting to cause a StackOverflowError potentially leading to denial of service. This issue affects Apache Qpid Broker-J through 10.0.1. Users are recommended to upgrade to version 10.1.0, which fixes the issue.
- CVE-2026-68074High
A pre-authentication attacker could leverage unbounded symbol value caching to cause resource exhaustion leading to denial of service. Affects Apache Qpid Broker-J through 10.0.1.
- CVE-2026-68060High
A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential denial of service. This issue affects Apache Qpid Broker-J through 10.0.1. Users are recommended to upgrade to version 10.1.0, which fixes the issue.
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.