CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. If you have a NetFraming based CoreWCF service, extra system resources could be consumed by connections being left established instead of closing or aborting them. There are two scenarios when this can happen. When a client established a connection to the service and sends no data, the service will wait indefinitely for the client to initiate the NetFraming session handshake. Additionally, once a client has established a session, if the client doesn't send any requests for the period of time configured in the binding ReceiveTimeout, the connection is not properly closed as part of the session being aborted. The bindings affected by this behavior are NetTcpBinding, NetNamedPipeBinding, and UnixDomainSocketBinding. Only NetTcpBinding has the ability to accept non local connections. The currently supported versions of CoreWCF are v1.4.x and v1.5.x. The fix can be found in v1.4.2 and v1.5.2 of the CoreWCF packages. Users are advised to upgrade. There are no workarounds for this issue.
References
Link | Resource |
---|---|
https://github.com/CoreWCF/CoreWCF/issues/1345 | Issue Tracking Product |
https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-32jq-mv89-5rx7 | Vendor Advisory |
https://github.com/CoreWCF/CoreWCF/issues/1345 | Issue Tracking Product |
https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-32jq-mv89-5rx7 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
09 Apr 2025, 15:34
Type | Values Removed | Values Added |
---|---|---|
CPE | cpe:2.3:a:corewcf:corewcf:1.4.1:*:*:*:*:*:*:* cpe:2.3:a:corewcf:corewcf:1.5.1:*:*:*:*:*:*:* |
|
References | () https://github.com/CoreWCF/CoreWCF/issues/1345 - Issue Tracking, Product | |
References | () https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-32jq-mv89-5rx7 - Vendor Advisory | |
First Time |
Corewcf corewcf
Corewcf |
21 Nov 2024, 09:06
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/CoreWCF/CoreWCF/issues/1345 - | |
References | () https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-32jq-mv89-5rx7 - |
21 Mar 2024, 20:15
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
|
Summary | (en) CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. If you have a NetFraming based CoreWCF service, extra system resources could be consumed by connections being left established instead of closing or aborting them. There are two scenarios when this can happen. When a client established a connection to the service and sends no data, the service will wait indefinitely for the client to initiate the NetFraming session handshake. Additionally, once a client has established a session, if the client doesn't send any requests for the period of time configured in the binding ReceiveTimeout, the connection is not properly closed as part of the session being aborted. The bindings affected by this behavior are NetTcpBinding, NetNamedPipeBinding, and UnixDomainSocketBinding. Only NetTcpBinding has the ability to accept non local connections. The currently supported versions of CoreWCF are v1.4.x and v1.5.x. The fix can be found in v1.4.2 and v1.5.2 of the CoreWCF packages. Users are advised to upgrade. There are no workarounds for this issue. |
15 Mar 2024, 19:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-03-15 19:15
Updated : 2025-04-09 15:34
NVD link : CVE-2024-28252
Mitre link : CVE-2024-28252
CVE.ORG link : CVE-2024-28252
JSON object : View
Products Affected
corewcf
- corewcf
CWE
CWE-404
Improper Resource Shutdown or Release