Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

GHSA-c6w8-7mp3-34j9

MEDIUM

GHSA-c6w8-7mp3-34j9 is a medium-severity (CVSS 6.3) Code Injection vulnerability in Microsoft.NETCore.App.Runtime.linux-arm. O3 Security confirms whether GHSA-c6w8-7mp3-34j9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

.NET Remote Code Execution Vulnerability

Also known asBIT-dotnet-2022-24512BIT-dotnet-sdk-2022-24512BIT-powershell-2022-24512CVE-2022-24512
Published
Oct 18, 2022
Updated
Jun 8, 2026
Affected
147 pkgs
Patched
147 / 147
Exploits
None indexed

Blast Radius

147 pkgs affected
.NETMicrosoft.NETCore.App.Runtime.linux-arm.NETMicrosoft.NETCore.App.Runtime.linux-arm64.NETMicrosoft.NETCore.App.Runtime.linux-musl-arm64.NETMicrosoft.NETCore.App.Runtime.linux-musl-x64.NETMicrosoft.NETCore.App.Runtime.linux-x64.NETMicrosoft.NETCore.App.Runtime.osx-x64.NETMicrosoft.NETCore.App.Runtime.win-arm.NETMicrosoft.NETCore.App.Runtime.win-arm64+139 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0, .NET 5.0, and .NET Core 3.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A Remote Code Execution vulnerability exists in .NET 6.0, .NET 5.0, and .NET Core 3.1 where a stack buffer overrun occurs in .NET Double Parse routine.

Patches

  • Any .NET 6.0 application running on .NET 6.0.2 or lower
  • Any .NET 5.0 application running on .NET 5.0.14 or lower
  • Any .NET Core 3.1 application running on .NET Core 3.1.22 or lower

To fix the issue, please install the latest version of .NET 6.0, .NET 5.0, or .NET Core 3.1. If you have installed one or more .NET Core SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET Core SDKs.

  • If you're using .NET 6.0, you should download and install Runtime 6.0.3 or SDK 6.0.103 (for Visual Studio 2019 v17.0) or SDK 6.0.201 (for Visual Studio 2019 V17.1) from https://dotnet.microsoft.com/download/dotnet-core/5.0.
  • If you're using .NET 5.0, you should download and install Runtime 5.0.15 or SDK 5.0.406 (for Visual Studio 2019 v16.11) or SDK 5.0.212 (for Visual Studio 2019 V16.9) from https://dotnet.microsoft.com/download/dotnet-core/5.0.
  • If you're using .NET Core 3.1, you should download and install Runtime 3.1.23 or SDK 3.1.417 (for Visual Studio 2019 v16.7) from https://dotnet.microsoft.com/download/dotnet-core/3.1. .NET 6.0, .NET 5.0, and .NET Core 3.1 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.

Other Details

Affected Packages

147 total 147 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.NETCore.App.Runtime.linux-arm3.0.0&&< 3.1.233.1.23
.NETNuGetMicrosoft.NETCore.App.Runtime.linux-arm643.0.0&&< 3.1.233.1.23
.NETNuGetMicrosoft.NETCore.App.Runtime.linux-musl-arm643.0.0&&< 3.1.233.1.23
.NETNuGetMicrosoft.NETCore.App.Runtime.linux-musl-x643.0.0&&< 3.1.233.1.23
.NETNuGetMicrosoft.NETCore.App.Runtime.linux-x643.0.0&&< 3.1.233.1.23
.NETNuGetMicrosoft.NETCore.App.Runtime.osx-x643.0.0&&< 3.1.233.1.23

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.NETCore.App.Runtime.linux-arm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Microsoft.NETCore.App.Runtime.linux-arm to 3.1.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c6w8-7mp3-34j9 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-c6w8-7mp3-34j9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-c6w8-7mp3-34j9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0, .NET 5.0, and .NET Core 3.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A Remote Code Execution vulnerability exists in .NET 6.0, .NET 5.0, and .NET Core 3.1 where a stack buffer overrun occurs in .NET Double Parse routine. ### Patches * Any .NET 6.0 application running on .NET 6.0.2 or lower * Any .NET 5.0 application running on .NET 5.0.14 or lower * Any .NET Core 3.1 application running on .NET Core 3.1.22 or
O3 Security · Impact-Aware SCA

Is GHSA-c6w8-7mp3-34j9 in your dependencies?

O3 detects GHSA-c6w8-7mp3-34j9 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.