SecurityTracker.com
    Home    |    View Topics    |    Search    |    Contact Us    |   

SecurityTracker
Archives


 


Category:   Application (VoIP)  >   Microsoft Skype Vendors:   Skype Technologies
Skype Error in Processing 'callto://' URLs Lets Remote Users Crash the Application
SecurityTracker Alert ID:  1010490
SecurityTracker URL:  http://securitytracker.com/id/1010490
CVE Reference:   CVE-2004-1114   (Links to External Site)
Updated:  Dec 1 2004
Original Entry Date:  Jun 14 2004
Impact:   Denial of service via network
Exploit Included:  Yes  
Version(s): 0.98.0.04
Description:   A vulnerability was reported in Skype in the processing of 'callto://' URLs. A remote user can cause the target user's application to crash.

Hillel Himovich reported that the following URL can trigger the flaw:

callto://aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/

The report indicates that it may be possible to execute arbitrary code, but this was not confirmed.

In November 2004, Fabian Becker reported a similar vulnerability in the quick-call field.

Impact:   A remote user can create a URL that, when loaded by the target user, will cause the target user's application to crash.
Solution:   No solution was available at the time of this entry.
Vendor URL:  www.skype.com/ (Links to External Site)
Cause:   Boundary error
Underlying OS:  Windows (Any)

Message History:   This archive entry has one or more follow-up message(s) listed below.
Nov 15 2004 (Vendor Issues Fix) Skype Error in Processing 'callto://' URLs Lets Remote Users Crash the Application
The vendor has issued a fix.



 Source Message Contents

Subject:  Skype URI callto username overflow




Here is a cute little URI I found crashing skype on it's latest version (0.98.0.04).
It's proboby a buffer overflow of some sort, so, a special crafted URI culd potentionally lead to remote code execution.
(would probobly be extreamly hard doing it threw a URI, but still an option)

callto://aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aa/

If you really really want this not to happend to you, u shuld remove the reffering registry entrance to "callto://" in URI's

Regards,
Hillel Himovich
"HLL"
HLL@netvision.net.il

 
 


Go to the Top of This SecurityTracker Archive Page





Home   |    View Topics   |    Search   |    Contact Us

This web site uses cookies for web analytics. Learn More

Copyright 2020, SecurityGlobal.net LLC