// back

Apache ActiveMQ Directory Traversal Vulnerability

06.21.10

BACKGROUND

Apache ActiveMQ is a messaging and enterprise integration patterns provider. The platform provides a Message Broker which handles communication between several different applications. Apache ActiveMQ supports many popular development languages including C/C++, Python, Java, and .NET. Apache ActiveMQ runs on a variety of platforms, including Windows, Linux and Solaris. For more information, see the vendor's site at the following link:

http://activemq.apache.org

DESCRIPTION

Remote exploitation of a directory traversal vulnerability in Apache Software Foundation's Apache ActiveMQ could allow an attacker to download files from a restricted directory, which can result in information disclosure.

The vulnerability is due to a failure by the Message Broker to restrict directory traversals. As a result, sensitive locations outside the configured Message Broker restricted directory can be accessed by an attacker. No authentication is required to access the ActiveMQ Message Broker service.

ANALYSIS

Exploitation of this vulnerability could allow an attacker to gain control over the affected machine.

By specifying a URL location with multiple directory traversal sequences such as "/../../", it is possible for an attacker to access sensitive files hosted on the Message Broker Server using the privileges associated with the Message Broker process. An attacker may be able to read important system files, which will result in information disclosure, and can potentially lead to full host compromise.

DETECTION

Apache ActiveMQ versions 5.3.1 and 5.3.2 are vulnerable.

WORKAROUND

A firewall rule may be setup on the Message Broker Server to restrict access to TCP port 8161.

VENDOR RESPONSE

Apache Software Foundation has released a fix which addresses this issue. Information about downloadable vendor updates can be found by clicking on the URLs shown.

https://issues.apache.org/jira/browse/AMQ-2788

CVE INFORMATION

A Mitre Corp. Common Vulnerabilities and Exposures (CVE) number has not been assigned yet.

DISCLOSURE TIMELINE

05/05/2010 Initial Contact
06/01/2010 Initial Response
06/21/2010 Coordinated public disclosure

CREDIT

This vulnerability was reported to iDefense by AbdulAziz Hariri.

Get paid for vulnerability research
http://labs.idefense.com/methodology/vulnerability/vcp.php

Free tools, research and upcoming events
http://labs.idefense.com/

LEGAL NOTICES

Copyright © 2011 Verisign, Inc.

Permission is granted for the redistribution of this alert electronically. It may not be edited in any way without the express written consent of iDefense. If you wish to reprint the whole or any part of this alert in any other medium other than electronically, please e-mail customer service for permission.

Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.