CVE-2024-28252
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.58 % · percentile 48.21 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
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.
Read the publisher's advisoryCoreWCF 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 advisoryCoreWCF 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 advisory### Impact 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. ### Patches 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. ### Workarounds There are no workarounds. ### References https://github.com/CoreWCF/CoreWCF/issues/1345
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.58 % · percentile 48.21 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2024-28252 · 15 Nov 2026 14:45:34 UTC
CVE-2024-28252 · 14 Nov 2026 16:37:01 UTC
CVE-2024-28252 · 13 Nov 2026 19:59:34 UTC
CVE-2024-28252 · 12 Nov 2026 18:18:51 UTC
CVE-2024-28252 · 10 Nov 2026 20:24:10 UTC
CVE-2024-28252 · 09 Nov 2026 21:04:24 UTC
CVE-2024-28252 · 08 Nov 2026 15:12:21 UTC
CVE-2024-28252 · 07 Nov 2026 16:07:52 UTC
CVE-2024-28252 · 06 Nov 2026 19:10:17 UTC
CVE-2024-28252 · 05 Nov 2026 22:49:22 UTC
CVE-2024-28252 · 05 Nov 2026 02:54:06 UTC
CVE-2024-28252 · 03 Nov 2026 16:59:18 UTC
CVE-2024-28252 · 02 Nov 2026 23:59:04 UTC
CVE-2024-28252 · 01 Nov 2026 23:58:58 UTC
CVE-2024-28252 · 01 Nov 2026 03:04:52 UTC
CVE-2024-28252 · 31 Oct 2026 01:52:30 UTC
CVE-2024-28252 · 29 Oct 2026 18:29:26 UTC
CVE-2024-28252 · 28 Oct 2026 19:55:37 UTC
CVE-2024-28252 · 27 Oct 2026 15:46:19 UTC
CVE-2024-28252 · 27 Oct 2026 00:23:05 UTC
CVE-2024-28252 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2024-0796 · Published
euvd · EUVD-2024-0796 · Published
euvd · EUVD-2024-0796 · Published
euvd · EUVD-2024-0796 · Published
euvd · EUVD-2024-0796 · Published
euvd · EUVD-2024-0796 · Published
euvd · EUVD-2024-0796 · Published
euvd · EUVD-2024-0796 · Published
euvd · EUVD-2024-0796 · Published
euvd · EUVD-2024-0796 · Published
nvd · CVE-2024-28252 · Published
osv · GHSA-32jq-mv89-5rx7 · Published
cve-program · CVE-2024-28252 · Published