Applies To.NET

Release Date:October 13, 2020

Version:.NET Framework 3.5 and 4.8

Summary

An information disclosure vulnerability exists when the .NET Framework improperly handles objects in memory. An attacker who successfully exploited the vulnerability could disclose contents of an affected system's memory. To exploit the vulnerability, an authenticated attacker would need to run a specially crafted application. The update addresses the vulnerability by correcting how the .NET Framework handles objects in memory.

To learn more about the vulnerabilities, go to the following Common Vulnerabilities and Exposures (CVE).

Known issues in this update

ASP.Net applications fail during precompilation with error message

Symptoms After you apply this October 13, 2020 Security and Quality Rollup for .NET Framework 4.8, some ASP.Net applications fail during precompilation. The error message that you receive will likely contain the words “Error ASPCONFIG.”Cause An invalid configuration state in either the “sessionState,” “anonymouseIdentification,” or “authentication/forms” sections of “System.web” configuration. This might occur during build-and-publish routines if configuration transformations leave the Web.config file in an intermediate state for precompilation.Workaround

This issue was resolved in KB4601055.

ASP.Net applications may not deliver cookieless tokens in the URI

Symptoms After you apply this October 1, 2020 Security and Quality Rollup for .NET Framework 4.8, some ASP.Net applications may not deliver cookieless tokens in the URI, possibly resulting in 302-redirect loops or lost or missing session state.Cause The ASP.Net features for Session State, Anonymous Identification, and Forms Authentication all rely on issuing tokens to a web client, and they all allow the option for those tokens to be delivered in a cookie or embedded in the URI for clients that don’t support cookies. The URI-embedding has long been an insecure and disrecommended practice and this KB quietly disables issuing tokens in URI’s unless one of these three features explicitly requests a cookie mode of “UseUri” in configuration. Configurations that specify “AutoDetect” or “UseDeviceProfile” may inadvertently result in attempted and failed embedding of these tokens in the URI.

Workaround

This issue was resolved in KB4601055.

How to get this update

Install this update

Release Channel

Available

Next Step

Windows Update and Microsoft Update

Yes

None. This update will be downloaded and installed automatically from Windows Update.

Microsoft Update Catalog

Yes

To get the standalone package for this update, go to the Microsoft Update Catalog website.

Windows Server Update Services (WSUS)

Yes

This update will automatically sync with WSUS if you configure Products and Classifications as follows:

Product:Windows 10, version 1809 and Windows Server, version 2019

Classification: Security Updates

File information

For a list of the files that are provided in this update, download the file information for cumulative update.

Additional information about this update

The following articles contain additional information about this update as it relates to individual product versions.

  • 4579976 Description of the Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows 10 Version 1809 for ARM64 (KB4579976)

Information about protection and security

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.