The following security advisory is sent to the securiteam mailing list, and can
be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion
The SecuriTeam alerts list - Free, Accurate, Independent.
Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html
- - - - - - - - -
Websphere MQ MCAUSER Setting Bypass Vulnerability
------------------------------------------------------------------------
SUMMARY
<http://www-306.ibm.com/software/integration/wmq/> Websphere MQ is an
Enterprise level application that can be used to provide a unified
platform for messaging within an organisation. IBM describes their
technology as follows:
"WebSphere MQ provides an award-winning messaging backbone for deploying
your enterprise service bus (ESB) today as the connectivity layer of a
service-orientated architecture (SOA)."
The Websphere MQ service can be used to transfer messages between systems
and applications. It is possible to lock down access to channels by
setting an invalid MCAUSER. A method of bypassing Websphere MQ service
authorization control has been discovered which would enable unauthorised
access to be gained.
DETAILS
Vulnerable Systems:
* Websphere MQ version 5.1 up to version 5.3 (Solaris)
* Websphere MQ version 6.0.0.0 (Windows)
Impact:
The vulnerability could enable an attacker to access sensitive channels
that have been restricted with the MCAUSER parameter. This would enable an
attacker to gain full read and write access to all queues defined within
the channel. Additionally, an attacker could perform remote fingerprinting
of the software, alter the Queue Manager configuration and potentially
execute Operating System commands through the creation of an appropriate
trigger process. The latter would be dependent on the presence of an
existing trigger monitor process running on the system. Additionally, on
version 6 of the software an attacker could create a service to execute
commands on the system.
Cause:
The vulnerability arises from an error in the state model responsible for
permitting connections to a channel. A connection can be established to
the Queue Manager if the "2035 Not Authorised" response is ignored and the
connection attempt continues.
Interim Workaround:
The workarounds at the present time involve using additional security
mechanisms such as Security Exits to protect all channels on a Queue
Manager. Additionally, it is possible to use network filtering to restrict
access to Websphere MQ services to trusted IP addresses only. It is also
possible that correctly deploying and mandating the use of SSL client
certificates will prevent an attacker from accessing the channels on the
Queue Manager. IBM have released a fix pack, the link of which is provided
below.
Solution:
IBM has released the following solution(s) and fix packs:
<http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037>
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
CVE Information:
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1130>
CVE-2008-1130
ADDITIONAL INFORMATION
The information has been provided by
<mailto:Elspeth.Levi@mwrinfosecurity.com> Elspeth Levi.
The original article can be found at:
<http://www.mwrinfosecurity.com/publications/mwri_websphere-mq-mcauser-setting-bypass-advisory_2008-03-26.pdf>
http://www.mwrinfosecurity.com/publications/mwri_websphere-mq-mcauser-setting-bypass-advisory_2008-03-26.pdf
========================================
This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to:
list-unsubscribe@securiteam.com
In order to subscribe to the mailing list, simply forward this email to:
list-subscribe@securiteam.com
====================
====================
DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any
kind.
In no event shall we be liable for any damages whatsoever including direct,
indirect, incidental, consequential, loss of business profits or special
damages.
