Vulnerabilities > CVE-2012-3467 - Improper Authentication vulnerability in Apache Qpid

047910
CVSS 5.0 - MEDIUM
Attack vector
NETWORK
Attack complexity
LOW
Privileges required
NONE
Confidentiality impact
NONE
Integrity impact
PARTIAL
Availability impact
NONE
network
low complexity
apache
CWE-287
nessus

Summary

Apache QPID 0.14, 0.16, and earlier uses a NullAuthenticator mechanism to authenticate catch-up shadow connections to AMQP brokers, which allows remote attackers to bypass authentication.

Common Weakness Enumeration (CWE)

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.

Nessus

  • NASL familyRed Hat Local Security Checks
    NASL idREDHAT-RHSA-2012-1279.NASL
    descriptionUpdated Messaging component packages that fix one security issue, multiple bugs, and add various enhancements are now available for Red Hat Enterprise MRG 2.2 for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. Red Hat Enterprise MRG (Messaging, Realtime, and Grid) is a next-generation IT infrastructure for enterprise computing. MRG offers increased performance, reliability, interoperability, and faster computing for enterprise customers. MRG Messaging is a high-speed reliable messaging distribution for Linux based on AMQP (Advanced Message Queuing Protocol), an open protocol standard for enterprise messaging that is designed to make mission critical messaging widely available as a standard service, and to make enterprise messaging interoperable across platforms, programming languages, and vendors. MRG Messaging includes an AMQP 0-10 messaging broker; AMQP 0-10 client libraries for C++, Java JMS, and Python; as well as persistence libraries and management tools. It was discovered that the Apache Qpid daemon (qpidd) did not require authentication for
    last seen2020-06-01
    modified2020-06-02
    plugin id76650
    published2014-07-22
    reporterThis script is Copyright (C) 2014-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/76650
    titleRHEL 6 : MRG Messaging (RHSA-2012:1279)
  • NASL familyRed Hat Local Security Checks
    NASL idREDHAT-RHSA-2012-1277.NASL
    descriptionUpdated Messaging component packages that fix two security issues, multiple bugs, and add various enhancements are now available for Red Hat Enterprise MRG 2.2 for Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section. Red Hat Enterprise MRG (Messaging, Realtime, and Grid) is a next-generation IT infrastructure for enterprise computing. MRG offers increased performance, reliability, interoperability, and faster computing for enterprise customers. MRG Messaging is a high-speed reliable messaging distribution for Linux based on AMQP (Advanced Message Queuing Protocol), an open protocol standard for enterprise messaging that is designed to make mission critical messaging widely available as a standard service, and to make enterprise messaging interoperable across platforms, programming languages, and vendors. MRG Messaging includes an AMQP 0-10 messaging broker; AMQP 0-10 client libraries for C++, Java JMS, and Python; as well as persistence libraries and management tools. It was discovered that the Apache Qpid daemon (qpidd) did not allow the number of connections from clients to be restricted. A malicious client could use this flaw to open an excessive amount of connections, preventing other legitimate clients from establishing a connection to qpidd. (CVE-2012-2145) To address CVE-2012-2145, new qpidd configuration options were introduced: max-negotiate-time defines the time during which initial protocol negotiation must succeed, connection-limit-per-user and connection-limit-per-ip can be used to limit the number of connections per user and client host IP. Refer to the qpidd manual page for additional details. It was discovered that qpidd did not require authentication for
    last seen2020-06-01
    modified2020-06-02
    plugin id76648
    published2014-07-22
    reporterThis script is Copyright (C) 2014-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/76648
    titleRHEL 5 : MRG Messaging (RHSA-2012:1277)

Redhat

advisories
  • rhsa
    idRHSA-2012:1277
  • rhsa
    idRHSA-2012:1279
rpms
  • mrg-release-0:2.2.0-1.el5
  • python-qpid-0:0.14-11.el5
  • python-qpid-qmf-0:0.14-14.el5
  • qpid-cpp-client-0:0.14-22.el5
  • qpid-cpp-client-devel-0:0.14-22.el5
  • qpid-cpp-client-devel-docs-0:0.14-22.el5
  • qpid-cpp-client-rdma-0:0.14-22.el5
  • qpid-cpp-client-ssl-0:0.14-22.el5
  • qpid-cpp-mrg-debuginfo-0:0.14-22.el5
  • qpid-cpp-server-0:0.14-22.el5
  • qpid-cpp-server-cluster-0:0.14-22.el5
  • qpid-cpp-server-devel-0:0.14-22.el5
  • qpid-cpp-server-rdma-0:0.14-22.el5
  • qpid-cpp-server-ssl-0:0.14-22.el5
  • qpid-cpp-server-store-0:0.14-22.el5
  • qpid-cpp-server-xml-0:0.14-22.el5
  • qpid-java-client-0:0.18-2.el5
  • qpid-java-common-0:0.18-2.el5
  • qpid-java-example-0:0.18-2.el5
  • qpid-jca-0:0.18-2.el5
  • qpid-jca-xarecovery-0:0.18-2.el5
  • qpid-qmf-0:0.14-14.el5
  • qpid-qmf-debuginfo-0:0.14-14.el5
  • qpid-qmf-devel-0:0.14-14.el5
  • qpid-tools-0:0.14-6.el5
  • ruby-qpid-qmf-0:0.14-14.el5
  • mrg-release-0:2.2.0-1.el6
  • python-qpid-qmf-0:0.14-14.el6_3
  • qpid-cpp-client-0:0.14-22.el6_3
  • qpid-cpp-client-devel-0:0.14-22.el6_3
  • qpid-cpp-client-devel-docs-0:0.14-22.el6_3
  • qpid-cpp-client-rdma-0:0.14-22.el6_3
  • qpid-cpp-client-ssl-0:0.14-22.el6_3
  • qpid-cpp-debuginfo-0:0.14-22.el6_3
  • qpid-cpp-server-0:0.14-22.el6_3
  • qpid-cpp-server-cluster-0:0.14-22.el6_3
  • qpid-cpp-server-devel-0:0.14-22.el6_3
  • qpid-cpp-server-rdma-0:0.14-22.el6_3
  • qpid-cpp-server-ssl-0:0.14-22.el6_3
  • qpid-cpp-server-store-0:0.14-22.el6_3
  • qpid-cpp-server-xml-0:0.14-22.el6_3
  • qpid-java-client-0:0.18-2.el6
  • qpid-java-common-0:0.18-2.el6
  • qpid-java-example-0:0.18-2.el6
  • qpid-jca-0:0.18-2.el6
  • qpid-jca-xarecovery-0:0.18-2.el6
  • qpid-qmf-0:0.14-14.el6_3
  • qpid-qmf-debuginfo-0:0.14-14.el6_3
  • qpid-qmf-devel-0:0.14-14.el6_3
  • ruby-qpid-qmf-0:0.14-14.el6_3
  • xerces-c-0:3.0.1-20.el6
  • xerces-c-debuginfo-0:3.0.1-20.el6
  • xerces-c-devel-0:3.0.1-20.el6
  • xerces-c-doc-0:3.0.1-20.el6
  • xqilla-0:2.2.3-8.el6
  • xqilla-debuginfo-0:2.2.3-8.el6
  • xqilla-devel-0:2.2.3-8.el6
  • xqilla-doc-0:2.2.3-8.el6

Seebug

bulletinFamilyexploit
descriptionBugtraq ID:54954 CVE ID:CVE-2012-3467 Apache Qpid (Open Source AMQP Messaging)是一个跨平台的企业通讯解决方案,实现了高级消息队列协议。 Apache Qpid C++库实现存在安全缺陷,允许在影子链接(shadow connections)中使用NullAuthenticator机制进行验证,导致AMQP客户端应用绕过验证访问broker。 0 bitcoind/Bitcoin-Qt 0.3.11之前版本 厂商解决方案 用户可参考如下供应商提供的安全公告获得补丁信息: http://svn.apache.org/viewvc?view=revision&revision=1352992
idSSV:60321
last seen2017-11-19
modified2012-08-13
published2012-08-13
reporterRoot
titleApache QPID NullAuthenticator验证绕过漏洞