You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
viewstate
About this tag
The viewstate tag on WindowsForum.com covers discussions about ASP.NET view state security, particularly in the context of SharePoint and IIS deployments. Recurring themes include deserialization vulnerabilities leading to remote code execution (RCE), such as those associated with CVE-2025-53770 and related advisories. Topics also include protection of machineKey material, encryption of view state data, and mitigation strategies like UrlScan rules and custom error mapping. The content focuses on enterprise IT security, patch management, and operational guidance for Windows Server and SharePoint environments. Users will find technical analysis of exploits, patch verification challenges, and practical steps to secure view state against tampering and information disclosure.
Microsoft’s SharePoint on-premises ecosystem is once again at the center of a high-risk security incident: an untrusted-deserialization remote code execution (RCE) class of weaknesses is being actively exploited against internet-facing SharePoint Server deployments, and an exact CVE identifier...
Microsoft's Internet Information Services (IIS) and its relationship with Windows Server have once again become a focus. Recent reports from Hong Kong and international media, along with practical feedback from community forums, show that as Microsoft continues to release security patches and...
The identifier CVE-2025-49712 does not appear in any public, authoritative advisory or vulnerability database at this time; the single URL you supplied resolves to Microsoft’s update guide infrastructure but returns no accessible content without JavaScript, and independent searches for...
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