CVE-2012-3467
First published: Thu Jun 28 2012(Updated: )
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] <a href="https://issues.apache.org/jira/browse/QPID-3849">https://issues.apache.org/jira/browse/QPID-3849</a> Relevant upstream patch: [2] <a href="http://svn.apache.org/viewvc?view=revision&revision=1352992">http://svn.apache.org/viewvc?view=revision&revision=1352992</a>
Credit: secalert@redhat.com secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Apache Qpid | <=0.16 | |
| Apache Qpid | =0.5 | |
| Apache Qpid | =0.6 | |
| Apache Qpid | =0.14 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://rhn.redhat.com/errata/RHSA-2012-1277.html
- http://rhn.redhat.com/errata/RHSA-2012-1279.html
- http://secunia.com/advisories/50186
- http://secunia.com/advisories/50698
- http://svn.apache.org/viewvc?view=revision&revision=1352992
- http://www.openwall.com/lists/oss-security/2012/08/09/6
- http://www.securityfocus.com/bid/54954
- https://bugzilla.redhat.com/show_bug.cgi?id=836276
- https://exchange.xforce.ibmcloud.com/vulnerabilities/77568
- https://issues.apache.org/jira/browse/QPID-3849
- https://rhn.redhat.com/errata/RHSA-2012-1277.html
- https://rhn.redhat.com/errata/RHSA-2012-1279.html
Frequently Asked Questions
What is the severity of CVE-2012-3467?
CVE-2012-3467 is rated as a medium severity vulnerability.
How do I fix CVE-2012-3467?
To fix CVE-2012-3467, upgrade Apache Qpid to the latest version above 0.16 or apply relevant patches provided by your vendor.
What versions of Apache Qpid are affected by CVE-2012-3467?
CVE-2012-3467 affects Apache Qpid versions up to 0.16 and specific versions 0.5, 0.6, and 0.14.
What is the impact of CVE-2012-3467?
The impact of CVE-2012-3467 may lead to unauthorized access and potential data exposure within the AMQP messaging scheme.
Is CVE-2012-3467 a network vulnerability?
Yes, CVE-2012-3467 is considered a network vulnerability due to its interaction with AMQP messaging and broker connections.
- collector/redhat-bugzilla
- alias/CVE-2012-3467
- collector/nvd-cve
- collector/nvd-index
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/type
- agent/weakness
- package-manager/redhat
- vendor/apache
- canonical/apache qpid
- version/apache qpid/0.16
- version/apache qpid/0.5
- version/apache qpid/0.6
- version/apache qpid/0.14