Skip to content

GHSA-3qf9-qxfj-4whc BIT-dotnet-2023-36792 BIT-dotnet-sdk-2023-36792 CVE-2023-36792

Microsoft Security Advisory CVE-2023-36792: .NET Remote Code Execution Vulnerability

High NuGet
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-190 Integer Overflow or Wraparound
Fix
Available
3 packages have a fixed version

Description

Microsoft Security Advisory CVE-2023-36792: .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/91944

<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 --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

.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

CVE-2023-36792

Revisions

V1.0 (September 12, 2023): Advisory published.

Version 1.0

Last Updated 2023-09-12

Affected versions

NuGet

PackageVulnerableFixed 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
>= 6.0.0, < 6.0.22
6.0.22
Microsoft.NETCore.App.Runtime.win-x86
>= 7.0.0, < 7.0.11
7.0.11

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 → 6.0.22

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-x86 --version 6.0.22

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-190: Integer Overflow or Wraparound

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How to prevent it
  • Requirements: Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
  • Requirements: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
  • Implementation: Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range. Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
  • Implementation: Understand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7] Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.
  • Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Implementation: Examine compiler warnings closely and eliminate problems with potential security implications, such as signed / unsigned mismatch in memory operations, or use of uninitialized variables. Even if the weakness is rarely exploitable, a single failure may lead to the compromise of the entire system.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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