|
Trillian Protocol Handling Buffer Overflow Vulnerabilities
|
|
Secunia Advisory:
|
SA10973
|
|
|
Release Date:
|
2004-02-25
|
|
Popularity:
|
11,306 views
|
|
|
Critical:
|
Moderately critical
|
|
Impact:
|
System access
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | Trillian 0.x
Trillian Pro 1.x
Trillian Pro 2.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Stefan Esser has discovered two vulnerabilities in Trillian, which can be exploited by malicious people to compromise a user's system.
An integer overflow exists in the handling of the AIM/Oscar Protocol when allocating memory for DirectIM packets. This can be exploited to corrupt the heap by sending a specially crafted DirectIM packet to a user's system.
A boundary error when parsing Yahoo packets can result in a buffer overflow. This can be exploited by sending a specially crafted YMSG packet with an overly long key name to a vulnerable system. Exploitation of this issue requires the ability to conduct a MitM attack (Man-in-the-Middle).
Successful exploitation of the vulnerabilities may allow execution of arbitrary code on a vulnerable system with the user's privileges.
The vulnerabilities have been reported in the following versions:
* Trillian 0.71 through 0.74F
* Trillian Pro 1.0
* Trillian Pro 2.0
* Trillian Pro 2.01
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
