CVE-2012-4446: Medium severity Apache qpid vulnerability
Florian Weimer of the Red Hat Product Security Team discovered that setting the federationtag attribute in an AMQP connection would turn the connection into a broker-to-broker connection, rather than a client-to-server connection. Because of this, incoming user IDs are not checked, so if a client were to set the federationtag attribute when establishing a regular AMQP connection, Qpid would no longer check the user ID on AMQP messages submitted by the client. The client can then supply any value and thus impersonate any user, since AMQP messages carry user information that identify the sender and message recipients, which use user names for authentication purposes. The client does have to authenticate, but any authentication method, including SASL ANONYMOUS would work.
Other sources
The default configuration for Apache Qpid 0.20 and earlier, when the federationtag attribute is enabled, accepts AMQP connections without checking the source user ID, which allows remote attackers to bypass authentication and have other unspecified impact via an AMQP request.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2012-4446?
CVE-2012-4446 is considered to be of medium severity due to the potential for remote attackers to bypass authentication.
How do I fix CVE-2012-4446?
To fix CVE-2012-4446, upgrade Apache Qpid to version 0.23 or later.
What versions of Apache Qpid are affected by CVE-2012-4446?
CVE-2012-4446 affects Apache Qpid versions 0.20 and earlier, as well as specific versions 0.5 through 0.19.
What impact does CVE-2012-4446 have on applications?
CVE-2012-4446 allows remote attackers to bypass authentication, potentially leading to unauthorized access to the application.
Is CVE-2012-4446 associated with a specific configuration option?
Yes, CVE-2012-4446 is related to the default configuration of Apache Qpid when the federation_tag attribute is enabled.