CVE-2024-28252

CoreWCF NetFraming based services can leave connections open when they should be closed

Workarounds

There are no workarounds.

References

https://github.com/CoreWCF/CoreWCF/issues/1345

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.

CVE-2024-28252 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.2, 1.5.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is CVE-2024-28252? CVE-2024-28252 is a high-severity security vulnerability in CoreWCF.NetFramingBase (nuget), affecting versions >= 1.4.0, < 1.4.2. It is fixed in 1.4.2, 1.5.2.
2. How severe is CVE-2024-28252? CVE-2024-28252 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of CoreWCF.NetFramingBase are affected by CVE-2024-28252? CoreWCF.NetFramingBase (nuget) versions >= 1.4.0, < 1.4.2 is affected.
4. Is there a fix for CVE-2024-28252? Yes. CVE-2024-28252 is fixed in 1.4.2, 1.5.2. Upgrade to this version or later.
5. Is CVE-2024-28252 exploitable, and should I be worried? Whether CVE-2024-28252 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-28252 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-28252?
   • Upgrade CoreWCF.NetFramingBase to 1.4.2 or later
   • Upgrade CoreWCF.NetFramingBase to 1.5.2 or later

Other vulnerabilities in CoreWCF.NetFramingBase