iDefense Security Advisory 01.15.08: TIBCO SmartSockets RTserver Heap Overflow Vulnerability
iDefense Security Advisory 01.15.08
http://labs.idefense.com/intelligence/vulnerabilities/
Jan 15, 2008
I. BACKGROUND
TIBCO SmartSockets is a message passing framework used to transport
messages over disparate channels. The RTserver is the server component
of the framework. More information can be found on the vendor's web
site at the following URL.
http://www.tibco.com/software/messaging/smartsockets/
II. DESCRIPTION
Remote exploitation of a heap overflow vulnerability in TIBCO Software
Inc.'s SmartSockets RTserver may allow an attacker to crash the service
or execute arbitrary code with SYSTEM privileges.
A heap overflow vulnerability exists within the code responsible for
processing requests. Two distinct values from the request are used for
the allocation size and the amount of data copied. Since both values
are attacker controlled, this can lead to a heap overflow, potentially
resulting in the execution of arbitrary code.
III. ANALYSIS
Exploitation allows an attacker to execute arbitrary code with SYSTEM
privileges. Unsuccessful attempts will likely crash the RTserver. The
service does not restart, which makes repeated exploitation attempts
more difficult.
The RTserver is the core component of the SmartSockets framework.
Without it, applications will be unable to pass messages.
IV. DETECTION
iDefense has confirmed the existence of this vulnerability in TIBCO
SmartSockets version 6.8.0. Previous versions may also be affected.
V. WORKAROUND
iDefense is currently unaware of any workarounds for this issue.
VI. VENDOR RESPONSE
TIBCO has addressed this vulnerability by releasing new versions of
their software. For more information, consult their advisory at the
following URL.
http://www.tibco.com/mk/advisory.jsp
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2007-5658 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org/), which standardizes names for
security problems.
VIII. DISCLOSURE TIMELINE
10/23/2007 Initial vendor notification
12/04/2007 Second vendor notification
12/05/2007 Initial vendor response
01/15/2008 Coordinated public disclosure
IX. CREDIT
This vulnerability was reported to VeriSign iDefense by McSlibin.
Get paid for vulnerability research
http://labs.idefense.com/methodology/vulnerability/vcp.php
Free tools, research and upcoming events
http://labs.idefense.com/
X. LEGAL NOTICES
Copyright © 2008 iDefense, 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 customerservice@xxxxxxxxxxxx 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.