Skip to content
fr Sign in
Not rated

CVE-2017-15702 In Apache Qpid Broker-J 0.18 through 0.32, if the broker is configured with different authentication providers on…

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.

Affected products and versions

Product Affected versions Fixed in
Apache Qpid Broker-J Versions not published

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Apache Qpid Broker-J

The 19 CVEs of Apache Qpid Broker-J →
CVE-2026-92550 A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential… Not rated CVE-2026-92560 A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential… Not rated CVE-2026-92573 Improper handling of compressed data in the shared GZIP decompressor used for AMQP 0-8/0-9/0-9-1 and AMQP 0-10 message… Not rated CVE-2026-92564 A pre-authentication attacker could leverage type nesting to cause a StackOverflowError potentially leading to denial of… Not rated
Track this CVE