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

GHSA-fr44-546p-7xcp

HIGH

MsQuic Remote Denial of Service Vulnerability

Also known asBIT-dotnet-2023-36435BIT-dotnet-sdk-2023-36435CVE-2023-36435
Published
Oct 10, 2023
Updated
Jun 3, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
5.5%probability of exploitation in next 30 days
Lower Risk92th percentile+2.96%
0.47%2.52%4.57%6.63%1.6%5.5%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected
.NETMicrosoft.Native.Quic.MsQuic.OpenSSL.NETMicrosoft.Native.Quic.MsQuic.Schannel

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

Impact

The MsQuic server will continue to leak memory until no more is available, resulting in a denial of service.

Patches

The following patch was made:

Workarounds

Beyond upgrading to the patched versions, there is no other workaround.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.Native.Quic.MsQuic.OpenSSLall versions2.2.3
.NETNuGetMicrosoft.Native.Quic.MsQuic.Schannelall versions2.2.3

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.Native.Quic.MsQuic.OpenSSL. 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.Native.Quic.MsQuic.OpenSSL to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fr44-546p-7xcp 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-fr44-546p-7xcp 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-fr44-546p-7xcp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The MsQuic server will continue to leak memory until no more is available, resulting in a denial of service. ### Patches The following patch was made: - Fix Memory Leak from Multiple Decodes of TP - https://github.com/microsoft/msquic/commit/d364feeda0dd8b729eca6fef149c1ef98630f0cb ### Workarounds Beyond upgrading to the patched versions, there is no other workaround.
O3 Security · Impact-Aware SCA

Is GHSA-fr44-546p-7xcp in your dependencies?

O3 detects GHSA-fr44-546p-7xcp across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.