Bug 1340803 (CVE-2016-4432) - CVE-2016-4432 qpid-java: Authentication bypass
Summary: CVE-2016-4432 qpid-java: Authentication bypass
Status: CLOSED WONTFIX
Alias: CVE-2016-4432
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=important,public=20160527,repo...
Keywords: Security
Depends On:
Blocks: 1340805
TreeView+ depends on / blocked
 
Reported: 2016-05-30 10:29 UTC by Andrej Nemec
Modified: 2019-06-08 21:14 UTC (History)
19 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2016-06-24 16:49:28 UTC


Attachments (Terms of Use)

Description Andrej Nemec 2016-05-30 10:29:40 UTC
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.

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.

External references:

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

References:

http://seclists.org/oss-sec/2016/q2/424

Comment 1 Kurt Seifried 2016-06-17 20:32:14 UTC
Satellite 6 uses client certificates to authenticate clients and does not rely upon qpid-java'[s internal authentication system.

Comment 2 Kurt Seifried 2016-06-24 16:49:28 UTC
Statement:

This issue did not affect the versions of the qpid -java broker as shipped with Red Hat MRG 2 and 3 and Satellite 6 as they did not use the access feature (e.g. Satellite 6 relies on client certificate authentication to control access).


Note You need to log in before you can comment on or make changes to this bug.