.NET Framework February Security and Quality Rollup

Tara Overfield

Tara

Today, we are releasing the February 2021 Security and Quality Rollup Updates for .NET Framework.

Security

CVE-2021-24111– .NET Framework Denial of Service Vulnerability

This security update addresses a denial of service vulnerability in .NET Framework. For more information please see CVE-2021-24111.

Quality and Reliability

This release contains the following quality and reliability improvements.

ASP.NET
  • Addresses an issue where after installing the update released on October 20th, some ASP.Net applications fail during precompilation – likely with a message that contains the words “Error ASPCONFIG.”
CLR1
  • Improves the reliability of automatic Native Image generation task.
WPF2
  • Addresses a hang when scrolling to the end of a TreeView, when layout rounding is enabled and DPI scaling is not 100%.

1 Common Language Runtime (CLR) 2 Windows Presentation Foundation (WPF)

Known issues in this update

SymptomAfter installing this update, WPF apps may crash with a callstack similar to

Exception Info: System.NullReferenceException at System.Windows.Interop.HwndMouseInputProvider.HasCustomChrome(System.Windows.Interop.HwndSource, RECT ByRef)
at System.Windows.Interop.HwndMouseInputProvider.GetEffectiveClientRect(IntPtr)
at System.Windows.Interop.HwndMouseInputProvider.PossiblyDeactivate(IntPtr, Boolean)
at System.Windows.Interop.HwndMouseInputProvider.Dispose()

This occurs when disposing an HwndSource whose RootVisual is null, a situation that arises in Visual Studio when docking or splitting windows, and could arise in other apps.

WorkaroundTo work around this problem, set two AppContext switches using one of the methods described in AppContext Class (System) under the heading “AppContext for library consumers”.  The switches are named

Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix and

Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix

and both should be set to “true”.   The first switch avoids the crash, but re-introduces the bug fixed in the KBs.  The second switch is currently ignored, but will be recognized in a future .NET update that contains a fix for the null-reference crash;  it restores the original bug fix.

For example, using the app.config file method to apply the workaround at application scope:

<AppContextSwitchOverrides 
value="Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true; 
Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true " />
ResolutionFor some Windows 10, version 1809, Windows Server 2019 and newer versions this issue is resolved in February 2021 Cumulative Update Preview

Getting the Update

The Security and Quality Rollup is available via Windows Update, Windows Server Update Services, and Microsoft Update Catalog. The Security Only Update is available via Windows Server Update Services and Microsoft Update Catalog.

Microsoft Update Catalog

You can get the update via the Microsoft Update Catalog. For Windows 10, NET Framework 4.8 updates are available via Windows Update, Windows Server Update Services, Microsoft Update Catalog. Updates for other versions of .NET Framework are part of the Windows 10 Monthly Cumulative Update.

**Note**: Customers that rely on Windows Update and Windows Server Update Services will automatically receive the .NET Framework version-specific updates. Advanced system administrators can also take use of the below direct Microsoft Update Catalog download links to .NET Framework-specific updates. Before applying these updates, please ensure that you carefully review the .NET Framework version applicability, to ensure that you only install updates on systems where they apply.

The following table is for Windows 10 and Windows Server 2016 and newer versions.

Product VersionCumulative Update
Windows 10, version 20H2 and Windows Server, version 20H2
.NET Framework 3.5, 4.8Catalog4601050
Windows 10 2004 and Windows Server, version 2004
.NET Framework 3.5, 4.8Catalog4601050
Windows 10 1909 and Windows Server, version 1909
.NET Framework 3.5, 4.8Catalog4601056
Windows 10 1809 (October 2018 Update) and Windows Server 20194601887
.NET Framework 3.5, 4.7.2Catalog4601060
.NET Framework 3.5, 4.8Catalog4601055
Windows 10 1803 (April 2018 Update)
.NET Framework 3.5, 4.7.2Catalog4601354
.NET Framework 4.8Catalog4601054
Windows 10 1703 (Creators Update)
.NET Framework 3.5, 4.7, 4.7.1, 4.7.2Catalog4601330
.NET Framework 4.8Catalog4601052
Windows 10 1607 (Anniversary Update) and Windows Server 2016
.NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2Catalog4601318
.NET Framework 4.8Catalog4601051

The following table is for earlier Windows and Windows Server versions.

Product VersionSecurity and Quality RollupSecurity Only Update
Windows 8.1, Windows RT 8.1 and Windows Server 2012 R246030044602960
.NET Framework 3.5Catalog4578953N/AN/A
.NET Framework 4.5.2Catalog4578956N/AN/A
.NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2Catalog4601048Catalog4601094
.NET Framework 4.8Catalog4601058Catalog4601092
Windows Server 201246030034602959
.NET Framework 3.5Catalog4578950N/AN/A
.NET Framework 4.5.2Catalog4578954N/AN/A
.NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2Catalog4600957Catalog4601093
.NET Framework 4.8Catalog4601057Catalog4601091
Windows 7 SP1 and Windows Server 2008 R2 SP146030024602958
.NET Framework 3.5.1Catalog4578952N/AN/A
.NET Framework 4.5.2Catalog4578955N/AN/A
.NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2Catalog4600945Catalog4601090
.NET Framework 4.8Catalog4600944Catalog4601089
Windows Server 200846030054602961
.NET Framework 2.0, 3.0Catalog4578951N/AN/A
.NET Framework 4.5.2Catalog4578955N/AN/A
.NET Framework 4.6Catalog4600945Catalog4601090

 

Previous Monthly Rollups

The last few .NET Framework Monthly updates are listed below for your convenience:

0 comments

Leave a comment