CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. If you have a…
Historical advisory recorded 24 Oct 2026 23:17:34 UTC. Read the latest advisory.
nvd · CVE-2024-28252
PublishedCoreWCF 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.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2024-28252
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-404
Original publisher date fields
published: 2024-03-15T19:15:07.210
lastModified: 2026-06-17T07:21:16.137
2 source CPE criteria · context only
- cpe:2.3:a:corewcf:corewcf:1.4.1:*:*:*:*:*:*:*
- cpe:2.3:a:corewcf:corewcf:1.5.1:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON