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-92609Critical
A session fixation vulnerability in HTTP management authentication in Apache Qpid Broker-J (through 10.1.0) allows remote attackers to gain unauthorized access to an authenticated management session by reusing a session identifier retained across successful authentication.
- CVE-2026-92573Medium
Apache Qpid Broker-J improperly handles compressed data in the shared GZIP decompressor used for AMQP 0-8/0-9/0-9-1 and AMQP 0-10 message delivery, message conversion, and HTTP management JSON rendering. An authenticated message producer can exhaust memory and disrupt broker availability by processing data without a decompressed-output limit.
- CVE-2026-92564High
Apache Qpid Broker-J is vulnerable to a pre-authentication attack where type nesting can cause a StackOverflowError. This can potentially lead to denial of service.
- CVE-2026-92560High
A vulnerability in Apache Qpid Broker-J (through 10.1.0) allows a pre-authentication attacker to leverage type size/count handling to cause excessive allocation. This can lead to a potential denial of service.
- CVE-2026-92550High
A vulnerability in Apache Qpid Broker-J (through 10.1.0) allows a pre-authentication attacker to leverage type size/count handling to cause excessive allocation. This can lead to a potential denial of service.
- CVE-2026-92608High
Improper handling of property-encoding exceptions during AMQP 1.0-to-AMQP 0-10 message conversion in Apache Qpid Broker-J (through 10.1.0) allows authenticated message producers to disrupt delivery to AMQP 0-10 consumers. This occurs via message properties that the target encoder does not handle correctly.
- 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.
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS