Revision Note: V1.2 (September 24, 2010): Added an entry to the FAQ to announce a revision to the workaround, "Enable a UrlScan or Request Filtering rule, enable ASP.NET custom errors, and map all error codes to the same error page." Customers who have already applied the workaround should...
active attacks
advisory
asp.net
customerrors
encryption
errorpage
faq
information
information disclosure
microsoft
request filtering
security
security breach
server issues
tampering
urlscan
viewstate
vulnerability
web.config
workaround