Doubleclick - round 3: the official response
|Better today than
never... We finally saw an official DoubleClick's answer :
"We are currently in the middle of completing our due diligence pertaining to this situation. We expect this to be completed next week; at which time we will begin to make the necessary changes in order to ensure that the site is secure"
Beware, this is not an official and public response. Nope, just an ordinary answer to those who continually ask DoubleClick : "hey bud, is it true that your servers are full of good old bugs ?"
So, they'll take one week to read what follows, and verify wether their servers are vulnerable to these good old tricks :
By the way, DoubleClick tells journalists who ask for some kind of precisions that nothing's vulnerable... As usual, DoubleClick's clients have nothing to fear.
If you want to exploit the bugs on the servers, you'll be a cracker and will go to jail (or something similar). We are no crackers. So we won't.
For those who are interested in cracking an who want to go to court and be condemned, here's the modus operandi which will prove that DoubleClick's servers are vulnerable, that one can put sniffers in it, and take back sensitive informations about their clients.
Scan all of the 188.8.131.52 IP address (from one to 254), look for IIS web servers (and NT servers which seem to be very tasteful). Test the unicode bug. Search the "Unitools" package in Bugtraq, which have been submitted by Roelof W Temmingh in a post on Thursday the 25 of january 2001. Launch the scripts... That's it... You've probably hacked DoubleClick. Upload the t00lz you want. In a few days, you'll have all the logins and passwords you'll ever want to posess, but never dare to ask for. In a few months, you'll be condemned for cybercriminality... But, at least, you'll prove that DoubleClick, if one closely read their oficial response, take every body for dummies.
Malade mental, bis repetita
Jean-Paul Ney condamné
et sur le Net...