Revised August 28, 2024: Update breaking change details to known issue section.
Revised July 30, 2024: Add breaking change information to known issue section.
Applies to:
Microsoft .NET Framework 4.8
REMINDER Windows Server 2008 R2 SP1 have reached the end of mainstream support and are now in extended security update (ESU) support.
Starting in July 2020, there will no longer be optional, non-security releases (known as "C" releases) for this operating system. Operating systems in extended support have only cumulative monthly security updates (known as the "B" or Update Tuesday release).
Verify that you have installed the required updates listed in the How to get this update section before installing this update.
Customers who have purchased the Extended Security Update (ESU) for on-premises versions of these operating systems must follow the procedures in KB4522133 to continue receiving security updates after extended support ends on January 14, 2020. For more information on ESU and which editions are supported, see KB4497181. For more information, see the ESU blog.
The July 9, 2024 update for Windows Server 2008 R2 SP1 includes cumulative security and reliability improvements in .NET Framework 4.8. We recommend that you apply this update as part of your regular maintenance routines. Verify that you have installed the required updates listed in the How to get this update section before installing this update.
Summary
Security Improvements
CVE-2024-38081 - .NET Framework Elevation of Privilege Vulnerability This security update addresses a remote code execution vulnerability detailed in CVE-2024-38081.
Quality and Reliability Improvements
|
Winforms |
- Addresses an issue with the size of memory leaks associated with AccessibleObjects held in memory due to ref-counting. |
Additional information about this update
The following articles contain additional information about this update as it relates to individual product versions.
-
5041021 Description of the Security and Quality Rollup for .NET Framework 3.5.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Server 2008 R2 SP1 (KB5041021)
Known issues in this update
|
Breaking change details |
The .NET Framework servicing update released on July 2024 security and quality rollup - .NET Framework contains a security fix addressed an elevation of privilege vulnerability detailed in CVE 2024-38081. The fix changed System.IO.Path.GetTempPath method return value. If windows version exposes the GetTempPath2 Win32 API, this method invokes that API and returns the resolved path. See the Remarks section of the GetTempPath2 documentation for more information on how this resolution is performed, including how to control the return value through the use of environment variables. The GetTempPath2 API may not be available on all versions of Windows. An observable difference between the GetTempPath and GetTempPath2 Win32 APIs is that they return different values for SYSTEM and non-SYSTEM processes. When calling this function from a process running as SYSTEM it will return the path %WINDIR%\SystemTemp, which is inaccessible to non-SYSTEM processes. This return value for SYSTEM processes cannot be overridden by environment variables. For non-SYSTEM processes, GetTempPath2 will behave the same as GetTempPath, respecting the same environment variables to override the return value. In some scenarios it may be possible to redirect the Temp folder to a different folder using environment variables or other means. Please refer to the official documentation for the GetTempPath2 Win32 API for the most up to date information on this behavior. Please reference to the System.IO.Path.GetTempPath API for more information. |
|
Temporary workaround |
⚠️ Warning: The opt-out will disable the security fix for the elevation of privilege vulnerability detailed in CVE 2024-38081. The opt-out is only for temporary workaround if you're sure that the software is running in secure environments. Microsoft does not recommend applying this temporary workaround.
|
|
Resolution |
The API behavior change is by design to address the elevation of privilege vulnerability. Any affected software or application is expected to make code change to adapt to this new design change. |
How to get this update
Before installing this update
Prerequisite:
To apply this update, you must have .NET Framework 4.8 installed.
You must install the updates listed below and restart your device before installing the latest Rollup. Installing these updates improves the reliability of the update process and mitigates potential issues while installing the Rollup and applying Microsoft security fixes.
-
The March 12, 2019 servicing stack update (SSU) (KB4490628). To get the standalone package for this SSU, search for it in the Microsoft Update Catalog. This update is required to install updates that are only SHA-2 signed.
-
The latest SHA-2 update (KB4474419) released September 10, 2019 or newer update. If you are using Windows Update, the latest SHA-2 update will be offered to you automatically. This update is required to install updates that are only SHA-2 signed. For more information on SHA-2 updates, see 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
-
To get this security update, you must reinstall the "Extended Security Updates (ESU) Licensing Preparation Package" (KB5016892) for Windows Server 2008 R2 SP1 that is dated August 8, 2022 even if you previously installed the ESU key. The ESU licensing preparation package will be offered to you from WSUS. To get the standalone package for ESU licensing preparation package, search for it in the Microsoft Update Catalog.
-
After you install the items above, we strongly recommend that you install the latest SSU.
For Windows Server 2008 R2 SP1, you must have the servicing stack update (SSU) (KB5017397) that is dated September 13, 2022 or later installed. For more information about the latest SSU updates, see ADV990001 | Latest Servicing Stack Updates. If you use Windows Update, the latest SSU will be offered to you automatically if you are an ESU customer. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.
-
Download the ESU MAK add-on key from the VLSC portal and deploy and activate the ESU MAK add-on key. If you use the Volume Activation Management Tool (VAMT) to deploy and activate keys, follow the instructions here.
IMPORTANT You do not need an additional key for deployment of the following:
-
You do not need to deploy an additional ESU key for Azure virtual machines (VMs), Azure Stack HCI.
-
For other Azure products such as Azure VMWare, Azure Nutanix solution Azure Stack (Hub, Edge), or for bring-your-own images on Azure for Windows Server 2008 SP2, and Windows Server 2008 R2 SP1 you do need to deploy the ESU key. The steps to install, activate, and deploy ESUs are the same for the fourth year of ESU coverage.
-
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 if you are an ESU customer. |
|
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 individual .NET Framework product update will be installed, as applicable, by applying the operating system update. For more information about operating system updates see additional information about this update section. |
Restart requirement
You may need to 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, see the Deployments tab of the Microsoft Security Response Center (MSRC) Security Update Guide.
Update replacement information
This update replaces previously released updates KB5037038 and KB5038288.
File Information
|
x86 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
x64 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
How to obtain help and support for this update
-
Help for installing updates: Windows Update FAQ
-
Protect yourself online and at home: Windows Security support
-
Local support according to your country: International Support
