Microsoft .NET Framework 4.8
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).
Quality and reliability improvements
- Addressed an issue with WCF services sometimes failing to start when starting multiple services concurrently.
- Addressed a regression introduced in .NET Framework 4.8, where Control.AccessibleName, Control.AccessibleRole, and Control.AccessibleDescription properties stopped working for the following controls:Label, GroupBox, ToolStrip, ToolStripItems, StatusStrip, StatusStripItems, PropertyGrid, ProgressBar, ComboBox, MenuStrip, MenuItems, DataGridView.
- Addressed a regression in accessible name for combo box items for data bound combo boxes. .NET Framework 4.8 started using type name instead of the value of the DisplayMember property as an accessible name, this improvement uses the DisplayMember again.
- Disabled resuse of AppPathModifier in ASP.Net control output.
- HttpCookie objects in the ASP.Net request context will be created with configured defaults for cookie flags instead of .NET-style primitive defaults to match the behavior of `new HttpCookie(name)`.
- Addressed a failure that sometimes occured when a user connects to one Azure SQL database, performed an enclave based operation, and then connected to another database under the same server that has the same Attestation URL and performed an enclave operation on the second server.
- Added a CLR config variable Thread_AssignCpuGroups (1 by default) that can be set to 0 to disable automatic CPU group assignment done by the CLR for new threads created by Thread.Start() and thread pool threads, such that an app may do its own thread-spreading.
- Addressed a rare data corruption that can occur when using new API’s such as Unsafe.ByteOffset<T> which are often used with the new Span types. The corruption could occur when a GC operation is performed while a thread is calling Unsafe.ByteOffset<T> from inside of a loop.
- Addressed an issue regarding timers with very long due times ticking down much sooner than expected when the AppContext switch "Switch.System.Threading.UseNetCoreTimer" is enabled.
1 Windows Communication Foundation (WCF)
2 Common Language Runtime (CLR)
- As a reminder to advanced IT administrators, updates to .NET Framework 3.5 for Windows 8.1 and Windows Server 2012 R2 should only be applied on systems where .NET Framework 3.5 is present and enabled. Customers who attempt to pre-install updates to .NET Framework 3.5 to offline images that do not contain the .NET Framework 3.5 product enabled will expose these systems to failures to enable .NET Framework 3.5 after the systems are online. For more extensive information about deploying .NET Framework 3.5, see Microsoft .NET Framework 3.5 Deployment Considerations.
- All updates for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2 require that update KB 2919355 is installed. We recommend that you install update KB 2919355 on your Windows 8.1-based, Windows RT 8.1-based, or Windows Server 2012 R2-based computer so that you receive updates in the future.
- If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.
Known issues in this security update
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.”
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.
Customers who observe new unexpected failures or functional issues can implement an application setting by adding (or merging) the following code to the application configuration file. Setting either “true” or “false” will avoid the issue. However, we recommend that you set this value to “true” for sites that do not rely on cookieless features.
<?xml version="1.0" encoding="utf-8" ?><configuration> <appSettings> <add key=”aspnet:DisableAppPathModifier” value=”true” /> </appSettings></configuration>
Additional information about this update
- 4579979 Description of the Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1, RT 8.1, and Windows Server 2012 R2 (KB4579979)
How to obtain and install the update
Before installing this update
To apply this update, you must have .NET Framework 4.8 installed.
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 8.1, RT 8.1, and Windows Server 2012 R2Classification: Security Updates
To apply this update, you must have .NET Framework 4.8 installed.
You must restart the computer after you apply this update if any affected files are being used. We recommend that you exit all .NET Framework-based applications before you apply this update.
Update deployment information
For deployment details for this security update, go to the following article in the Microsoft Knowledge Base:
20201013 Security update deployment information: October 13, 2020
Update removal information
Note We do not recommend that you remove any security update. To remove this update, use the Programs and Features item in Control Panel.
Update restart information
This update does not require a system restart after you apply it unless files that are being updated are locked or are being used.
Update replacement information
This update replaces previously released updates 4576630.
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables.
Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2 file information
The MANIFEST files (.manifest) and MUM files (.mum) that are installed are not listed.