CVE-2023-35390: .NET and Visual Studio Remote Code Execution Vulnerability

Published Aug 2, 2023
·
Updated

.NET and Visual Studio Remote Code Execution Vulnerability

Other sources

Microsoft Security Advisory CVE-2023-35390: .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 when some dotnet commands are used in directories with weaker permissions which can result in remote code execution.

Announcement

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/266

<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.1xx SDK 7.0.109 or earlier. Any .NET 7.0.3xx SDK 7.0.306 or earlier. Any .NET 6.0.1xx SDK 6.0.120 or earlier. Any .NET 6.0.3xx SDK 6.0.315 or earlier. Any .NET 6.0.4xx SDK 6.0.412 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.NET.Build.Containers | <= 7.0.306 | 7.0.307, 7.0.400

<a name=".NET 6"></a>.NET 6

Package name | Affected version | Patched version ------------ | ---------------- | -------------------------

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.10 or SDK 7.0.110 (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.21 or SDK 6.0.316 (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

CVE-2023-35390

Revisions

V1.0 (August 08, 2023): Advisory published.

Version 1.0

Last Updated 2023-08-08

GitHub

Remote Code Execution: When running some dotnet commands(e.g. dotnet help add), dotnet attempts to locate and initiate a new process using cmd.exe. However, it prioritizes searching for cmd.exe in the current working directory (CWD) before checking other locations. This can potentially lead to the execution of malicious code;

Red Hat

Affected Software

23 affected componentsFixes available
Microsoft .NET 6.0
ubuntu/dotnet6<6.0.121-0ubuntu1~23.04.1
6.0.121-0ubuntu1~23.04.1
ubuntu/dotnet6<6.0.21
6.0.21
ubuntu/dotnet6<6.0.121-0ubuntu1~22.04.1
6.0.121-0ubuntu1~22.04.1
ubuntu/dotnet7<7.0.110-0ubuntu1~23.04.1
7.0.110-0ubuntu1~23.04.1
ubuntu/dotnet7<7.0.10
7.0.10
ubuntu/dotnet7<7.0.110-0ubuntu1~22.04.1
7.0.110-0ubuntu1~22.04.1
redhat/.NET SDK<6.0.121
6.0.121
redhat/.NET SDK<7.0.110
7.0.110
redhat/.NET Runtime<6.0.21
6.0.21
redhat/.NET Runtime<7.0.10
7.0.10
Microsoft .NET 7.0
nuget/Microsoft.NET.Build.Containers<=7.0.306
7.0.307
Microsoft .NET>=6.0.0<6.0.21
Microsoft .NET>=7.0.0<7.0.10
Microsoft Visual Studio 2022>=17.2.0<17.2.18
Microsoft Visual Studio 2022>=17.4.0<17.4.10
Microsoft Visual Studio 2022>=17.6.0<17.6.6
Microsoft .NET 7.0<7.0.10
7.0.10
Microsoft Visual Studio 2022=17.2
17.2.18
Microsoft .NET 6.0<6.0.21
6.0.21
Microsoft Visual Studio 2022=17.4
17.4.10
Microsoft Visual Studio 2022=17.6
17.6.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/dotnet6 to a version that resolves this vulnerability.

    Fixed in 6.0.121-0ubuntu1~23.04.1
  2. Upgrade

    Upgrade ubuntu/dotnet6 to a version that resolves this vulnerability.

    Fixed in 6.0.21
  3. Upgrade

    Upgrade ubuntu/dotnet6 to a version that resolves this vulnerability.

    Fixed in 6.0.121-0ubuntu1~22.04.1
  4. Upgrade

    Upgrade ubuntu/dotnet7 to a version that resolves this vulnerability.

    Fixed in 7.0.110-0ubuntu1~23.04.1
  5. Upgrade

    Upgrade ubuntu/dotnet7 to a version that resolves this vulnerability.

    Fixed in 7.0.10
  6. Upgrade

    Upgrade ubuntu/dotnet7 to a version that resolves this vulnerability.

    Fixed in 7.0.110-0ubuntu1~22.04.1
  7. Upgrade

    Upgrade redhat/.NET SDK to a version that resolves this vulnerability.

    Fixed in 6.0.121
  8. Upgrade

    Upgrade redhat/.NET SDK to a version that resolves this vulnerability.

    Fixed in 7.0.110
  9. Upgrade

    Upgrade redhat/.NET Runtime to a version that resolves this vulnerability.

    Fixed in 6.0.21
  10. Upgrade

    Upgrade redhat/.NET Runtime to a version that resolves this vulnerability.

    Fixed in 7.0.10
  11. Upgrade

    Upgrade nuget/Microsoft.NET.Build.Containers to a version that resolves this vulnerability.

    Fixed in 7.0.307
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 7.0.10Patch KB5029689
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.2.18
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.0.21Patch KB5029688
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.4.10
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.6.6
  17. Upgrade

    Upgrade .NET 6.0 to a version that resolves this vulnerability.

    Fixed in 6.0.316
  18. Upgrade

    Upgrade .NET 6.0 Runtime to a version that resolves this vulnerability.

    Fixed in 6.0.21
  19. Upgrade

    Upgrade .NET 7.0 to a version that resolves this vulnerability.

    Fixed in 7.0.110
  20. Upgrade

    Upgrade .NET 7.0 Runtime to a version that resolves this vulnerability.

    Fixed in 7.0.10
  21. Upgrade

    Upgrade Microsoft.AspNetCore.App to a version that resolves this vulnerability.

    Fixed in 6.0.5
  22. Upgrade

    Upgrade Microsoft.NETCore.App to a version that resolves this vulnerability.

    Fixed in 6.0.5
  23. Upgrade

    Upgrade Microsoft.WindowsDesktop.App to a version that resolves this vulnerability.

    Fixed in 6.0.5
  24. Operational

    After installing the updated runtime or SDK, restart your apps for the update to take effect.

Event History

Aug 8, 2023
CVE Published
via Ubuntu·12:00 AM
Data Sourced
07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
CVE Published
via MITRE·05:08 PM
Data Sourced
via MITRE·05:08 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 9, 2023
Advisory Published
via GitHub·01:15 PM
Jan 12, 2024
Data Sourced
via Launchpad·12:21 AM
Description
Data Sourced
via Debian·12:22 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2023-35390?

CVE-2023-35390 is a .NET and Visual Studio Remote Code Execution Vulnerability.

2

What is the severity of CVE-2023-35390?

CVE-2023-35390 has a severity value of 7.8, which is considered high.

3

Which software and versions are affected by CVE-2023-35390?

CVE-2023-35390 affects Microsoft Visual Studio 2022 versions 17.2 to 17.4, .NET 6.0 versions 6.0.0 to 6.0.21, and .NET 7.0 versions 7.0.0 to 7.0.10.

4

How do I fix the CVE-2023-35390 vulnerability in Visual Studio 2022?

To fix the CVE-2023-35390 vulnerability in Visual Studio 2022, you should update to version 17.4 or higher by downloading the patch from the Visual Studio website.

5

How do I fix the CVE-2023-35390 vulnerability in .NET 6.0 and 7.0?

To fix the CVE-2023-35390 vulnerability in .NET 6.0 and 7.0, you should update to the latest version by downloading the patch from the official Microsoft website.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203