mirror of
https://github.com/wiremock/WireMock.Net.git
synced 2026-01-11 13:00:33 +01:00
[security] Insecure transitive dependency to Microsoft.AspNetCore.Server.Kestrel.Core #718
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Kielek on GitHub (Oct 15, 2025).
Describe the bug
Related to version 1.14.0 and probably other to.
WireMock.Net --> WireMock.Net.Minimal ----.NET Framework/.NET Standard-----> Microsoft.AspNetCore v2.2.0 ----> Microsoft.AspNetCore.Server.Kestrel.Core v2.2.0
This package contains critical security issue (9.9/10) https://github.com/advisories/GHSA-5rrx-jjjq-q2r5.
Expected behavior:
The easiest way is to bump Microsoft.AspNetCore to 2.3.0.
Test to reproduce
Just compile your code with following switches
Other related info
It will be great to make the release shortly after the changes.
@Kielek commented on GitHub (Oct 17, 2025):
@StefH, I have check it more deeply.
It might be not so trivial to update. To fully resolve this particular issue
Microsoft.AspNetCoreshould be to2.3.0(2.2.0is out of support) together withMicrosoft.AspNetCore.Server.Kestrel.Coreto2.3.6. All this inWireMock.Net.Minimalfor .NET Framework 4.6.1 , .NET Standard 2.0 and 2.1.But it is not so simple. Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.Protocols property is marked as internal in this package version and it is conditionally set
AspNetCoreSelfHostclass.What is more
Microsoft.AspNetCore.Http.HttpResponsedoes not implementSupportsTrailers()andAppendTrailer(). Both needed byOwinResponseMapper.There is more vulnerable dependencies in .NET Framework 4.5.1 and 4.5.2 and .NET Standard 1.3 - but all of them are our of support by the Microsoft.
Internally, I have tried to bump
Microsoft.AspNetCore.Server.Kestrel.Coreto2.3.6in OpenTelemetry test suite. As there are binary breaking changes in minor versions it basically is not working.Looking forward for any recommendation/fixes you could provide. If there will be no possibility to fix without breaking chnages, I would consider 2.0 version with dropping support for anything older than .NET Standard 2.0/.NET Framework 4.6.2/.NET8.
@StefH commented on GitHub (Oct 17, 2025):
My plan is indeed to drop a lot of framework support.
Can you check this PR?
https://github.com/wiremock/WireMock.Net/pull/1359
And validate if this could solve this issue?
@Kielek commented on GitHub (Oct 17, 2025):
Unfortunately, I still need to maintain packages targeted to .NET Framework 4.6.2. It will be great to keep this support also by next 2 years. Then updating to 4.7.
I will check your changes shortly.
@StefH commented on GitHub (Nov 23, 2025):
@Kielek
Could you check it?
@Kielek commented on GitHub (Nov 24, 2025):
I reviewed your PR already https://github.com/wiremock/WireMock.Net/pull/1359#issuecomment-3416912874 and I do not see any new big changes in this PR. Am I missing something?