Skip to content

.NET Remote Code Execution Vulnerability

High severity GitHub Reviewed Published Jun 13, 2023 in dotnet/sdk • Updated Jul 30, 2024

Package

nuget Microsoft.NetCore.App.Runtime.linux-arm (NuGet)

Affected versions

>= 7.0.0, <= 7.0.5

Patched versions

7.0.7
nuget Microsoft.NetCore.App.Runtime.linux-arm64 (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.linux-musl-arm (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.linux-musl-arm64 (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.linux-musl-x64 (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.linux-x64 (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.osx-arm64 (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.osx-x64 (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.win-arm (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.win-arm64 (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.win-x64 (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7
nuget Microsoft.NetCore.App.Runtime.win-x86 (NuGet)
>= 7.0.0, <= 7.0.5
7.0.7

Description

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

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

A vulnerability exists in .NET source generator for P/Invokes that can lead to generated code freeing uninitialized memory and crashing.

Announcement

Announcement for this issue can be found at dotnet/announcements#253

Mitigation factors

Microsoft has not identified any mitigating factors for this vulnerability.

Affected software

  • Any .NET 7.0.1xx SDK 7.0.106 or earlier.
  • Any .NET 7.0.3xx SDK 7.0.303 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.linux-arm >= 7.0.0, <= 7.0.5 7.0.7
Microsoft.NetCore.App.Runtime.linux-arm64 >= 7.0.0, <= 7.0.5 7.0.7
Microsoft.NetCore.App.Runtime.linux-musl-arm >= 7.0.0, <= 7.0.5 7.0.7
Microsoft.NetCore.App.Runtime.linux-musl-arm64 >= 7.0.0, <= 7.0.5 7.0.7
Microsoft.NetCore.App.Runtime.linux-musl-x64 >= 7.0.0, <= 7.0.5 7.0.7
Microsoft.NetCore.App.Runtime.linux-x64 >= 7.0.0, <= 7.0.5 7.0.7
Microsoft.NetCore.App.Runtime.osx-arm64 >= 7.0.0, <= 7.0.5 7.0.7
Microsoft.NetCore.App.Runtime.osx-x64 >= 7.0.0, <= 7.0.5 7.0.7
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

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 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 are a library author and have used one of the affected versions listed above, please update, recompile, and redistribute your libraries.
  • If you have .NET 7.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 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 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-33128

Revisions

V1.0 (June 13, 2023): Advisory published.

Version 1.0

Last Updated 2023-06-13

References

@rbhanda rbhanda published to dotnet/sdk Jun 13, 2023
Published by the National Vulnerability Database Jun 14, 2023
Published to the GitHub Advisory Database Jun 14, 2023
Reviewed Jun 14, 2023
Last updated Jul 30, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.144%
(51st percentile)

Weaknesses

CVE ID

CVE-2023-33128

GHSA ID

GHSA-x469-cv7m-77r9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.