Not rated
CVE-2016-8741 The Apache Qpid Broker for Java can be configured to use different so called AuthenticationProviders to handle user…
Description
The Apache Qpid Broker for Java can be configured to use different so called AuthenticationProviders to handle user authentication. Among the choices are the SCRAM-SHA-1 and SCRAM-SHA-256 AuthenticationProvider types. It was discovered that these AuthenticationProviders in Apache Qpid Broker for Java 6.0.x before 6.0.6 and 6.1.x before 6.1.1 prematurely terminate the SCRAM SASL negotiation if the provided user name does not exist thus allowing remote attacker to determine the existence of user accounts. The Vulnerability does not apply to AuthenticationProviders other than SCRAM-SHA-1 and SCRAM-SHA-256.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Apache Qpid Broker-J | 6.1.0 | No fix stated |
References
- 1037537 www.securitytracker.com
- issues.apache.org issues.apache.org
- 95136 www.securityfocus.com
- [apache-qpid-users] 20161228 [CVE-2016-8741] Apache Qpid Broker for Java - Information Leakage qpid.2158936.n2.nabble.com
Timeline
- Published
- 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