Trillian is a multi-protocol chat application that supports IRC, ICQ, AIM and MSN protocols. More information can be found on the vendor's site at the following URL.
Remote exploitation of a heap overflow vulnerability in Cerulean Studios Trillian Instant Messenger could allow attackers to execute arbitrary code as the currently logged on user.
The vulnerability specifically exists due to improper handling of UTF-8 sequences. When word-wrapping UTF-8 text, the window width is improperly used as a buffer size value. As such, heap corruption can occur leading to a potentially exploitable condition.
Exploitation of this vulnerability could allow remote attackers to execute arbitrary code with the credentials of the currently logged on user.
Exploitation occurs simply by viewing a malicious message that contains a specially constructed UTF-8 string.
The MSN protocol is a known attack vector for this vulnerability. However, exploitation could potentially occur using any supported protocol.
iDefense has confirmed the existence of this vulnerability in Cerulean Studios Trillian 188.8.131.52. Previous versions are suspected to be vulnerable.
iDefense is currently unaware of any effective workaround for this issue.
The Cerulean Studios team has addressed this vulnerability by releasing version 184.108.40.206 of Trillian. More information is available at the Cerulean Studios Blog via the following URL.
A Mitre Corp. Common Vulnerabilities and Exposures (CVE) number has not been assigned yet.
05/04/2007 Initial vendor notification
05/04/2007 Initial vendor response
06/18/2007 Coordinated public disclosure
This vulnerability was reported to iDefense by www.BlurredLogic.com.
Get paid for vulnerability research
Free tools, research and upcoming events
Copyright © 2007 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.