Browsing bugtraq "news" (in fact on insecure.org), i ve found this:
http://seclists.org/lists/bugtraq/2005/Mar/0112.html
Funny. Is this problem introduced on Windows XP by SP2 or it was there previously and i didnt notice? i swear that MS fixed this problem years ago.
Altough is a severe error (bad problem tracking) i dont think we need to worry about that, since we use to run Windows protected by a firewall.
Or am i wrong?
Maybe someone from inside can explore this.