Headline
GHSA-88q2-h5g3-p4pg: .NET Remote Code Execution Vulnerability
Microsoft Security Advisory CVE-2023-24897: .NET Remote Code Execution Vulnerability
<a name="executive-summary"></a>Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 7.0 and .NET 6.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
This security update addresses a vulnerability in the MSDIA SDK where corrupted PDBs can cause heap overflow, leading to a crash or remove code execution
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/260
<a name="mitigation-factors"></a>Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
<a name="affected-software"></a>Affected software
- Any .NET 7.0 application running on .NET 7.0.5 or earlier.
- Any .NET 6.0 application running on .NET 6.0.16 or earlier.
If your application uses the following package versions, ensure you update to the latest version of .NET.
<a name=".NET 7"></a>.NET 7
Package name | Affected version | Patched version |
---|---|---|
Microsoft.NetCore.App.Runtime.win-arm | >= 7.0.0, <= 7.0.5 | 7.0.7 |
Microsoft.NetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.5 | 7.0.7 |
Microsoft.NetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.5 | 7.0.7 |
Microsoft.NetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.5 | 7.0.7 |
<a name=".NET 6"></a>.NET 6
Package name | Affected version | Patched version |
---|---|---|
Microsoft.NetCore.App.Runtime.win-arm | >= 6.0.0, <= 6.0.16 | 6.0.18 |
Microsoft.NetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.16 | 6.0.18 |
Microsoft.NetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.16 | 6.0.18 |
Microsoft.NetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.16 | 6.0.18 |
Advisory FAQ
<a name="how-affected"></a>How do I know if I am affected?
If you have a runtime or SDK with a version listed, or an affected package listed in affected software, you’re exposed to the vulnerability.
<a name="how-fix"></a>How do I fix the issue?
- To fix the issue please install the latest version of .NET 6.0 or .NET 7.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
- If you are using one of the affected packages, please update to the patched version listed above.
- If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the
dotnet --info
command. You will see output like the following;
.NET Core SDK (reflecting any global.json):
Version: 6.0.300
Commit: 8473146e7d
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.300\
Host (useful for support):
Version: 6.0.5
Commit: 8473146e7d
.NET Core SDKs installed:
6.0.300 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
- If you’re using .NET 7.0, you should download and install Runtime 7.0.7 or SDK 7.0.106 (for Visual Studio 2022 v17.4) from https://dotnet.microsoft.com/download/dotnet-core/7.0.
- If you’re using .NET 6.0, you should download and install Runtime 6.0.18 or SDK 6.0.312 (for Visual Studio 2022 v17.2) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
.NET 6.0 and and .NET 7.0 updates are also available from Microsoft Update. To access this either type “Check for updates” in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you’ve deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
Other Information
Reporting Security Issues
If you have found a potential security issue in .NET 6.0 or .NET 7.0, please email details to [email protected]. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
Disclaimer
The information provided in this advisory is provided “as is” without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
External Links
Revisions
V1.0 (June 13, 2023): Advisory published.
Version 1.0
Last Updated 2023-06-13
Microsoft Security Advisory CVE-2023-24897: .NET Remote Code Execution Vulnerability****Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 7.0 and .NET 6.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
This security update addresses a vulnerability in the MSDIA SDK where corrupted PDBs can cause heap overflow, leading to a crash or remove code execution
Announcement
Announcement for this issue can be found at dotnet/announcements#260
Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
Affected software
- Any .NET 7.0 application running on .NET 7.0.5 or earlier.
- Any .NET 6.0 application running on .NET 6.0.16 or earlier.
If your application uses the following package versions, ensure you update to the latest version of .NET.
.NET 7
Package name
Affected version
Patched version
Microsoft.NetCore.App.Runtime.win-arm
>= 7.0.0, <= 7.0.5
7.0.7
Microsoft.NetCore.App.Runtime.win-arm64
>= 7.0.0, <= 7.0.5
7.0.7
Microsoft.NetCore.App.Runtime.win-x64
>= 7.0.0, <= 7.0.5
7.0.7
Microsoft.NetCore.App.Runtime.win-x86
>= 7.0.0, <= 7.0.5
7.0.7
.NET 6
Package name
Affected version
Patched version
Microsoft.NetCore.App.Runtime.win-arm
>= 6.0.0, <= 6.0.16
6.0.18
Microsoft.NetCore.App.Runtime.win-arm64
>= 6.0.0, <= 6.0.16
6.0.18
Microsoft.NetCore.App.Runtime.win-x64
>= 6.0.0, <= 6.0.16
6.0.18
Microsoft.NetCore.App.Runtime.win-x86
>= 6.0.0, <= 6.0.16
6.0.18
Advisory FAQ****How do I know if I am affected?
If you have a runtime or SDK with a version listed, or an affected package listed in affected software, you’re exposed to the vulnerability.
How do I fix the issue?
To fix the issue please install the latest version of .NET 6.0 or .NET 7.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
If you are using one of the affected packages, please update to the patched version listed above.
If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the dotnet --info command. You will see output like the following;
.NET Core SDK (reflecting any global.json):
Version: 6.0.300 Commit: 8473146e7d
Runtime Environment:
OS Name: Windows OS Version: 10.0.18363 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\6.0.300\
Host (useful for support):
Version: 6.0.5 Commit: 8473146e7d
.NET Core SDKs installed:
6.0.300 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs: https://aka.ms/dotnet-download
- If you’re using .NET 7.0, you should download and install Runtime 7.0.7 or SDK 7.0.106 (for Visual Studio 2022 v17.4) from https://dotnet.microsoft.com/download/dotnet-core/7.0.
- If you’re using .NET 6.0, you should download and install Runtime 6.0.18 or SDK 6.0.312 (for Visual Studio 2022 v17.2) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
.NET 6.0 and and .NET 7.0 updates are also available from Microsoft Update. To access this either type “Check for updates” in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you’ve deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
Other Information****Reporting Security Issues
If you have found a potential security issue in .NET 6.0 or .NET 7.0, please email details to [email protected]. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
Disclaimer
The information provided in this advisory is provided “as is” without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
External Links
CVE-2023-24897
Revisions
V1.0 (June 13, 2023): Advisory published.
Version 1.0
Last Updated 2023-06-13
References
- GHSA-88q2-h5g3-p4pg
- https://nvd.nist.gov/vuln/detail/CVE-2023-24897
- dotnet/announcements#260
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-24897
Related news
.NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability
The June 2023 Patch Tuesday security update included fixes for a bypass for two previously addressed issues in Microsoft Exchange and a critical elevation of privilege flaw in SharePoint Server.
Categories: Exploits and vulnerabilities Categories: News Tags: Microsoft Tags: patch Tuesday Tags: CVE-2023-29357 Tags: CVE-2023-29363 Tags: CVE-2023-32014 Tags: CVE-2023-32015 Tags: CVE-2023-32013 Tags: CVE-2023-24897 Tags: CVE-2023-32031 Tags: SharePoint Tags: PGM Tags: Exchange Tags: Hyper-V Patch Tuesday of June 2023 is relatively relaxed. No actively exploited zero-days and only six critical vulnerabilities. (Read more...) The post Microsoft fixes six critical vulnerabilities in June Patch Tuesday appeared first on Malwarebytes Labs.