Apache Qpid Java Broker Authentication Flaw Lets Remote Users Cause the Target Service to Crash
SecurityTracker Alert ID: 1035982|
SecurityTracker URL: http://securitytracker.com/id/1035982
(Links to External Site)
Date: May 27 2016
Denial of service via network|
Fix Available: Yes Vendor Confirmed: Yes |
Version(s): 6.0.0, 6.0.1, 6.0.2|
A vulnerability was reported in Apache Qpid. A remote user can cause the target service to crash.|
A remote user can attempt authentication with specially crafted data to cause the target Qpid Java Broker to crash.
Systems with the broker configured to allow plaintext passwords are affected.
Alex Szczuczko of Red Hat, Inc. reported this vulnerability.
A remote user can cause the target service to crash.|
The vendor has issued a fix (6.0.3).|
The vendor's advisory is available at:
Vendor URL: qpid.apache.org/ (Links to External Site)
|Underlying OS: Linux (Any), UNIX (Any)|
Source Message Contents
Subject: [CVE-2016-3094] Apache Qpid Java Broker denial of service vulnerability|
CVE-2016-3094: Apache Qpid Java Broker denial of service vulnerability
Vendor: The Apache Software Foundation
Versions Affected: Qpid Java Broker versions 6.0.0, 6.0.1, and 6.0.2
Description: A malformed authentication attempt may cause the broker to
terminate. The Qpid Java Broker supports a number of configurable
authentication providers each supporting various SASL mechanisms. Some
mechanisms need (or can be configured to accept) plain-text passwords
being sent to the Broker (using the SASL "PLAIN" mechanism). Where the
broker has been configured to allow plain-text passwords for authentication
it is possible for a client to send a malformed authentication attempt
will lead the broker to terminate due to an uncaught Exception.
Brokers configured to use authentication from the "PlainPasswordFile",
"SimpleLDAP", or "Base64MD5PasswordFile" providers are vulnerable if the
"PLAIN" mechanism is enabled (by default "PLAIN" will be disabled on
non-TLS ports, but enabled on TLS connections).
Mitigation: Users should upgrade their Qpid Java Broker to version 6.0.3 or
later. If this is not possible, users can disable the PLAIN mechanism for
their authentication manager on versions 0.32 and later by adding
the list of disabledMechanisms on their authentication provider object.
Note that the SimpleLDAP authentication provider requires PLAIN and so this
work around does not apply there.
Credit: This issue was discovered by Alex Szczuczko of Red Hat, Inc.