MS emergency fix plugs ASP.Net web development hole
Yellow alert over severe server peril
Microsoft has released an out-of-cycle patch designed to address a serious flaw in its ASP.Net web application development toolkit.
The vulnerability, which has been under active attack for several weeks, creates a mechanism for attackers to read any file on a web application server. Microsoft rates the flaw as only "important", while independent security watchers such the the SANS Institute's Internet Storm Centre say that rating underestimates the risk posed by the flaw to online shops built using Microsoft's developer tools. The ISC has raised the InfoCon status of the flaw from green to yellow.
Microsoft's advisory provides more detail on the "information disclosure" flaw. It explains that "in Microsoft .NET Framework 3.5 Service Pack 1 and above, this vulnerability can be used by an attacker to retrieve the contents of any file within the ASP.NET application, including web.config" and that "this vulnerability can also be used for data tampering, which, if successfully exploited, could be used to decrypt and tamper with the data encrypted by the server".
Redmond decided the problem was too severe to wait for the next scheduled Patch Tuesday, 12 October, meriting an unusual but not unprecedented decision to release an out-of-cycle patch (MS10-070) instead.
The vulnerability stems from a cryptographic weakness, specifically involving improper error handling during encryption padding verification.
Attacks based on this weakness could allow a hacker to decrypt sniffed cookies or forge authentication tickets, among other attacks. Researchers Thai Duong and Juliano Rizzo discovered the flaw and presented a Padding Oracle Exploit Tool that illustrated the risk during a presentation at the Ekoparty conference in Argentina last month. ®
ok, im fairly sure this issue was made public at a blackhat security conference (without informing microsoft) on Fri 17th, work arounds and alternative protection was provided by MS on 20th and a full patch by the 28th,
i think they handled it superbly for once
Nothing to do with .NET's cryptographic strength...
"The vulnerability stems from a cryptographic weakness, specifically involving improper error handling during encryption padding verification.".
I wish the IT press would get it's facts straight instead of bandying around sensationalist crap like this .
This has nothing to do with a cryptographic weakness, this is about ASP.NET revealing too much useful information when a CryptographicException is thrown.
Every heard of Hotfixes ?
What they could do is to push out a hotfix two days after recognizing a problem and skip extensive testing for that. Users would make the deployment/non-deployment decision themselves.
Competent users have a sandbox where they can test a patch without affecting production.
Two weeks later the "highly tested/officially sanctioned" version of the patch would be distributed as an automatic update.