bugtraq - [CVE-2016-8741] Apache Qpid Broker for Java

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAP3WMuRfNFoaJKXAfSTJCSjRqO+0ss0Qp-YktBtOyMaX2miYAg@mail.gmail.com>
Date: Wed, 28 Dec 2016 11:50:51 +0000
From: Oleksandr Rudyy <orudyy@...il.com>
To: bugtraq@...urityfocus.com
Subject: [CVE-2016-8741] Apache Qpid Broker for Java - Information Leakage

[CVE-2016-8741] Apache Qpid Broker for Java - Information Leakage

Vendor: The Apache Software Foundation

Versions Affected: Apache Qpid Broker for Java versions 6.0.1,
                   6.0.2, 6.0.3, 6.0.4, 6.0.5, and 6.1.0

Description:

The 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 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.

Resolution:

Users should upgrade the Qpid Broker for Java to version 6.0.6,
6.1.1, or later (recommended).

Mitigation:

If upgrading is not possible, the vulnerability can be mitigated
by using an AuthenticationProvider other than SCRAM-SHA-1 and
SCRAM-SHA-256.

References:

https://issues.apache.org/jira/browse/QPID-7599