TIBCO Enterprise Message Service™vulnerability
Original release date: January 15, 2008
Last revised: --
Source: TIBCO Software Inc.
TIBCO would like to extendits appreciation to McSlibin and Sean Larsson (iDefense Labs) for discovery of these vulnerabilities, which have been addressed in the 4.4.2release.
TIBCO Enterprise Message Service vulnerability
Original release date: January 15, 2008
Last revised: --
Source: TIBCO Software Inc.
Systems Affected
TIBCO Enterprise Message Service (EMS) versions 4.0.0 through 4.4.1
The following components are affected:
* TIBCO EMS Server (tibemsd)
Overview
The TIBCO EMS server contains a buffer overflow vulnerability in
processing of inbound data via SmartSockets. The impact of this
vulnerability may include remote execution of arbitrary code,
information disclosure, and denial of service.
I. Description
TIBCO has released an update which addresses a critical vulnerability
in the server component of TIBCO EMS when used in conjunction with
TIBCO SmartSockets. This vulnerability affects the EMS server if an
attacker controls the SmartSockets Server, or is able to inject data
into the TCP stream between the SmartSockets and EMS servers. TIBCO
strongly recommends sites running the affected component to install
the update or take mitigating action as appropriate.
II. Impact
The impact of this vulnerability varies depending on the operating
system, configuration options of the server, and the privilege
levels of the user that invokes the server.
On Unix based systems, the successful exploit will allow arbitrary
code execution with the privileges of the user that invoked the
server.
On Windows based systems, the successful exploit will allow
arbitrary code execution with the privileges of the user that
invoked the server. If the server component is installed as a
system service, this will result in access to system privileges.
III. Solution
SmartSockets support in the EMS server is disabled by default.
If SmartSockets support has been enabled, upgrade TIBCO EMS to
version 4.4.2 or above. This is strongly recommended.
If an upgrade is not possible, the following actions can mitigate
the vulnerability:
* Disable SmartSockets support by setting "tibss_transports"
to "disabled" in the configuration file for the EMS server
(tibemsd.conf).
* Ensure that all SmartSockets servers specified in the
"server_names" field of the transports configuration file
(transports.conf) are fully trusted, and that injection of
data into the rtserver/tibemsd connection is prevented.
References
http://www.tibco.com/mk/advisory.jsp
---------------------------------------------------------------------
TIBCO would like to extend its appreciation to McSlibin and Sean
Larsson (iDefense Labs) for discovery of these vulnerabilities, which
have been addressed in the 4.4.2 release.
---------------------------------------------------------------------
The information on this page is being provided toyou on an "AS IS" and "AS-AVAILABLE" basis. The issues described on this page may or may not impact your system(s). TIBCO makes no representations, warranties, or guarantees as to the informationcontained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE AREHEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT TIBCO SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THEINFORMATION CONTAINED HEREIN. The information on this page is being provided to you under the terms of your license and/or services agreement with TIBCO, and may be used only for the purposes contemplated by the agreement.If you do not have such an agreement with TIBCO, this information is provided under the TIBCO.com Terms of Use, and may be used only for the purposes contemplated by such Terms ofUse.