Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Fri, 27 May 2016 16:17:33 +0100
From: Keith W <keith.wall@...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-4432] Apache Qpid Java Broker - authentication bypass

[CVE-2016-4432] Apache Qpid Java Broker - authentication bypass

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected: Qpid Java Broker versions 6.0.2 and earlier

Description:

The code responsible for handling incoming AMQP 0-8, 0-9, 0-91, and
0-10 connections contains a flaw that allows authentication to be
bypassed.  An remote attacker can exploit this vulnerability to
perform actions, without the need to specify valid credentials.  For
instance, unauthorised messages could be injected or messages stolen.

The vulnerability cannot be exploited if the Access Control List (ACL)
feature is enabled AND access to all virtual hosts controlled.

The vulnerability does not apply to the Broker's AMQP 1.0 support.

The vulnerability does not apply if the Broker is configured to
require SSL client authentication for all messaging connections.

Resolution:

Users should upgrade the Qpid Java Broker to version 6.0.3 or later
(recommended).

Mitigation:

If upgrading is not possible, the vulnerability can be mitigated using
an ACL file containing "ACCESS VIRTUALHOST" clauses that white-lists
user access to all virtualhosts.

If AMQP 0-8, 0-9, 0-91, and 0-10 support is not required, the
vulnerability can also be mitigated by turning off these protocols at
the Port level.

References:

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

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.