Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommend updating to msquic 2.4.8 #113136

Open
GrabYourPitchforks opened this issue Mar 4, 2025 · 1 comment
Open

Recommend updating to msquic 2.4.8 #113136

GrabYourPitchforks opened this issue Mar 4, 2025 · 1 comment
Labels
area-System.Net.Quic untriaged New issue has not been triaged by the area owner

Comments

@GrabYourPitchforks
Copy link
Member

The msquic folks recently released v2.4.8. Though this was not a security release, it does contain some defense-in-depth improvements related to how library load occurs.

Because of this, there's a risk that third-party vulnerability scanners may start to mark versions prior to 2.4.8 as suspicious, and that might cause false positive alerts for our customers. We should get ahead of this by proactively pulling 2.4.8 into our builds. There's no need for us to make a servicing release just for this, but it'd be good to get the update to come along for the ride the next time we have a scheduled servicing release.

Relatedly, .NET 8.0.x currently takes a dependency on msquic v2.3.x. The 2.3.x branch exits support in Sep 2025, well ahead of .NET 8's end of life. We should update the 8.0.x branch to keep ahead of any end-of-life mismatches here.

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Mar 4, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Net.Quic untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

1 participant