CVE-2024-28252 — CoreWCF.NetFramingBase
HIGHCVE-2024-28252 is a high-severity (CVSS 7.5) CWE-404 vulnerability in CoreWCF.NetFramingBase. A fix is available for CoreWCF.NetFramingBase — see the affected versions and patch details below.
CoreWCF NetFraming based services can leave connections open when they should be closed
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-28252.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
CoreWCF.NetFramingBase.NETCoreWCF.NetFramingBaseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | CoreWCF.NetFramingBase | ≥ 1.4.0&&< 1.4.2 | 1.4.2dotnet add package CoreWCF.NetFramingBase --version 1.4.2 |
| .NETNuGet | CoreWCF.NetFramingBase | ≥ 1.5.0&&< 1.5.2 | 1.5.2dotnet add package CoreWCF.NetFramingBase --version 1.5.2 |
Affected Products
corewcfcorewcfDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CoreWCF.NetFramingBase, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update CoreWCF.NetFramingBase to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-28252 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2024-28252 in your dependencies?
Find it across NuGet, including transitive dependencies.