I believe that the critical ASP.NET framework update that Microsoft pushed just before the new year was to fix this issue as well, amongst a few others.

http://technet.microsoft.com/en-us/security/bulletin/ms11-10...