Difference between revisions of "ASP.NET POET Vulnerability"

From OWASP
Jump to: navigation, search
(Not reccomended Fixes (via web.config change))
(Not reccomended Fixes (via web.config change))
Line 10: Line 10:
  
 
Why we do not reccomend these workarounds
 
Why we do not reccomend these workarounds
* ["T" exploit 200 vs 404 response status]: http://blog.mindedsecurity.com/2010/10/breaking-net-encryption-with-or-without.html
+
* ["T" exploit 200 vs 404 response status]: http://www.gdssecurity.com/l/b/2010/10/04/padbuster-v0-3-and-the-net-padding-oracle-attack/
 
* ["T" exploit attack]: http://blog.mindedsecurity.com/2010/10/breaking-net-encryption-with-or-without.html
 
* ["T" exploit attack]: http://blog.mindedsecurity.com/2010/10/breaking-net-encryption-with-or-without.html
  

Revision as of 15:06, 4 October 2010

Contents

This page contains details about the ASP.NET POET vulnerability disclosed on 2010-09-17. This vulnerability exists in all versions of ASP.NET (all versions released through 2010-09-18). As of 2010-09-20, there is no fix available to resolve the vulnerability; in the meantime, Microsoft strongly urges all ASP.NET deployments perform the recommended workaround to mitigate the vulnerability in the short-term.

Advisory

Not reccomended Fixes (via web.config change)

Why we do not reccomend these workarounds

Blogs, News, Articles

discussion Threads