GHSA-g4p8-g7mq-wpx4 BIT-dotnet-2023-36793 BIT-dotnet-sdk-2023-36793 CVE-2023-36793
Microsoft Security Advisory CVE-2023-36793: .NET Remote Code Execution Vulnerability
- Severity
- 7.8 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 1.23%
- Chance of exploitation in the next 30 days. Higher than 68.82% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-122 Heap-based Buffer Overflow
- Fix
- Available
- 3 packages have a fixed version
Description
Microsoft Security Advisory CVE-2023-36793: .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.
A vulnerability exists in Microsoft.DiaSymReader.Native.amd64.dll when reading a corrupted PDB file which may lead to remote code execution. This issue only affects Windows systems.
Note: The vulnerabilities CVE-2023-36792, CVE-2023-36793, CVE-2023-36792, CVE-2023-36796 are all resolved by a single patch. Get affected software to resolve all of them.
Discussion
Discussion for this issue can be found at https://github.com/dotnet/runtime/issues/91947
<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.10 or earlier.
- Any .NET 6.0 application running on .NET 6.0.21 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-arm64 | >= 7.0.0, <= 7.0.10 | 7.0.11 |
| Microsoft.NETCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.10 | 7.0.11 |
| Microsoft.NETCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.10 | 7.0.11 |
<a name=".NET 6"></a>.NET 6
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.NETCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.21 | 6.0.22 |
| Microsoft.NETCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.21 | 6.0.22 |
| Microsoft.NETCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.21 | 6.0.22 |
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 --infocommand. 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.11 or SDK 7.0.111 (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.22 or SDK 6.0.317 (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 secure@microsoft.com. 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 (September 12, 2023): Advisory published.
Version 1.0
Last Updated 2023-09-12
Affected versions
NuGet
| Package | Vulnerable | Fixed in |
|---|---|---|
| Microsoft.NETCore.App.Runtime.win-arm64 | >= 7.0.0, < 7.0.11 |
7.0.11 |
| Microsoft.NETCore.App.Runtime.win-arm64 | >= 6.0.0, < 6.0.22 |
6.0.22 |
| Microsoft.NETCore.App.Runtime.win-x64 | >= 7.0.0, < 7.0.11 |
7.0.11 |
| Microsoft.NETCore.App.Runtime.win-x64 | >= 6.0.0, < 6.0.22 |
6.0.22 |
| Microsoft.NETCore.App.Runtime.win-x86 | >= 7.0.0, < 7.0.11 |
7.0.11 |
| Microsoft.NETCore.App.Runtime.win-x86 | >= 6.0.0, < 6.0.22 |
6.0.22 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
Microsoft.NETCore.App.Runtime.win-arm64 NuGet → 7.0.11
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-arm64 --version 7.0.11
Microsoft.NETCore.App.Runtime.win-x64 NuGet → 7.0.11
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-x64 --version 7.0.11
Microsoft.NETCore.App.Runtime.win-x86 NuGet → 7.0.11
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-x86 --version 7.0.11
Severity breakdown
CVSS 3.1 7.8
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-122: Heap-based Buffer Overflow
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How to prevent it
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Architecture and Design: Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Operation, Build and Compilation: Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Operation, Build and Compilation: Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].
- Implementation: Implement and perform bounds checking on input.
- Implementation: Do not use dangerous functions such as gets. Look for their safe equivalent, which checks for the boundary.
- Operation: Use OS-level preventative functionality. This is not a complete solution, but it provides some defense in depth.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| CVE-2020-1147 .NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability | High Known exploited | Also affects Microsoft.NETCore.App.Runtime.win-arm64 |
| GHSA-87vj-4hqv-22p9 Microsoft Security Advisory CVE-2026-96233 - .NET and Visual Studio Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.win-arm64 |
| GHSA-4mpw-cpwj-hxxj Microsoft Security Advisory CVE-2026-70197 - .NET and Visual Studio Remote Code Execution Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.win-arm64 |
| GHSA-3rxq-g8rj-r2cf Microsoft Security Advisory CVE-2026-69651 - .NET and Visual Studio Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.win-arm64 |
| GHSA-wxxw-5cvc-53j7 Microsoft Security Advisory CVE-2026-66822 - .NET and Visual Studio Information Disclosure Vulnerability | Medium | Also affects Microsoft.NETCore.App.Runtime.win-arm64 |
| GHSA-mc4q-93x5-f6hj Microsoft Security Advisory CVE-2026-58280 - .NET and Visual Studio Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.win-arm64 |
| GHSA-m93f-wj8c-rp8p Microsoft Security Advisory CVE-2026-62901 – .NET Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.win-arm64 |
| GHSA-c494-m2fq-59mx Microsoft Security Advisory CVE-2026-62898 – .NET Information Disclosure Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.win-arm64 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor