Trillian IRC Module Buffer Overflow Vulnerability
BID:5389
Info
Trillian IRC Module Buffer Overflow Vulnerability
| Bugtraq ID: | 5389 |
| Class: | Failure to Handle Exceptional Conditions |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Aug 02 2002 12:00AM |
| Updated: | Aug 02 2002 12:00AM |
| Credit: | Discovery of this vulnerability credited to Josh ([email protected]) and omega ([email protected]). |
| Vulnerable: |
Cerulean Studios Trillian 0.725 Cerulean Studios Trillian 0.73 |
| Not Vulnerable: | |
Discussion
Trillian IRC Module Buffer Overflow Vulnerability
A remotely exploitable buffer overflow condition has been reported in the Trillian IRC module. This issue is due to insufficient bounds checking of DCC Chat message length.
An attacker can exploit this vulnerability by sending a victim user a DCC Chat message of excessive length (4282+ characters). An attacker may potentially exploit this condition to cause locations in memory to be overwritten with attacker-supplied values, leading to execution of arbitrary code.
This may also cause the Trillian client to crash thereby leading to a denial of service condition.
A remotely exploitable buffer overflow condition has been reported in the Trillian IRC module. This issue is due to insufficient bounds checking of DCC Chat message length.
An attacker can exploit this vulnerability by sending a victim user a DCC Chat message of excessive length (4282+ characters). An attacker may potentially exploit this condition to cause locations in memory to be overwritten with attacker-supplied values, leading to execution of arbitrary code.
This may also cause the Trillian client to crash thereby leading to a denial of service condition.
Exploit / POC
Trillian IRC Module Buffer Overflow Vulnerability
Currently we are not aware of any exploits for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Currently we are not aware of any exploits for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.