Bug 836276 (CVE-2012-3467) - CVE-2012-3467 qpid-cpp-server-cluster: unauthorized broker access caused by the use of NullAuthenticator catch-up shadow connections
Summary: CVE-2012-3467 qpid-cpp-server-cluster: unauthorized broker access caused by t...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2012-3467
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 834608
Blocks: 767033 817177
TreeView+ depends on / blocked
 
Reported: 2012-06-28 14:35 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:53 UTC (History)
9 users (show)

Fixed In Version: qpid-cpp 0.17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-19 20:16:23 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1277 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging 2.2 update 2012-09-19 21:18:49 UTC
Red Hat Product Errata RHSA-2012:1279 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging 2.2 update 2012-09-19 21:29:24 UTC

Description Jan Lieskovsky 2012-06-28 14:35:38 UTC
In the AMQP messaging scheme implementation each broker can have both, direct connections and shadow connections. A shadow connection represents a connection to another broker in the cluster. Members use shadow connections to simulate the actions of other brokers, so that all members arrive at the same time. Output for shadow connections is just discarded, brokers only send data to their directly-connected clients.

A security flaw was found in the way the Apache Qpid C++ implementation performed authentication of connections creating "catch-up" shadow connections, which are used when broker joins the cluster. An AMQP client could use this to fake shadow connections to the AMQP broker. This issue was caused by using NullAuthenticator mechanism for authenticating these "catch-up" shadow connection and was fixed by making broker require authentication.

Upstream ticket:
[1] https://issues.apache.org/jira/browse/QPID-3849

Relevant upstream patch:
[2] http://svn.apache.org/viewvc?view=revision&revision=1352992

Comment 3 errata-xmlrpc 2012-09-19 17:21:38 UTC
This issue has been addressed in following products:

  MRG for RHEL-5 v. 2

Via RHSA-2012:1277 https://rhn.redhat.com/errata/RHSA-2012-1277.html

Comment 4 errata-xmlrpc 2012-09-19 17:30:38 UTC
This issue has been addressed in following products:

  MRG for RHEL-6 v.2

Via RHSA-2012:1279 https://rhn.redhat.com/errata/RHSA-2012-1279.html


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