[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAP3WMuR0Fztm3EMKT_-4+7Avo25Mf2TrYsXEqi9LOFzPAm0hJQ@mail.gmail.com>
Date: Wed, 28 Dec 2016 11:47:11 +0000
From: Oleksandr Rudyy <orudyy@...il.com>
To: "users@...d.apache.org" <users@...d.apache.org>, "dev@...d.apache.org" <dev@...d.apache.org>,
"security@...che.org" <security@...che.org>, oss-security@...ts.openwall.com,
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
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
