# CVE-2024-28252: CoreWCF NetFraming based services can leave connections open when they should be closed > Attackers can exhaust system resources by leaving NetFraming connections open, causing denial of service in CoreWCF services. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Mar 2024 - **Updated:** 26 Aug 2024 - **Also known as:** GHSA-32jq-mv89-5rx7 ## What is CVE-2024-28252? CVE-2024-28252 is a high-severity denial of service vulnerability in CoreWCF, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-404 (Improper Resource Shutdown or Release) ## Which versions are affected by CVE-2024-28252? 4 open source packages ship an affected version, including CoreWCF.NetFramingBase. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `CoreWCF.NetFramingBase` | NuGet | From 1.4.0 | 1.4.2 | | `CoreWCF.NetFramingBase` | NuGet | From 1.4.0 | 1.4.2 | | `CoreWCF.NetFramingBase` | NuGet | From 1.5.0 | 1.5.2 | | `CoreWCF.NetFramingBase` | NuGet | From 1.5.0 | 1.5.2 | Products: Corewcf Corewcf. ## How do I fix CVE-2024-28252? Upgrade CoreWCF.NetFramingBase to a fixed version for your release line: 1.4.2 or 1.5.2. ## Is CVE-2024-28252 being exploited? There is no known exploitation of CVE-2024-28252 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-28252 and fix it if it is affected. What it is: CVE-2024-28252 is a high-severity denial of service vulnerability in CoreWCF, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-28252 in the wild and no public exploit code. Affected packages and fixed versions: - CoreWCF.NetFramingBase (NuGet): affected from 1.4.0; fixed in 1.4.2 - CoreWCF.NetFramingBase (NuGet): affected from 1.4.0; fixed in 1.4.2 - CoreWCF.NetFramingBase (NuGet): affected from 1.5.0; fixed in 1.5.2 - CoreWCF.NetFramingBase (NuGet): affected from 1.5.0; fixed in 1.5.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-28252/ (Markdown: https://insights.sbomify.com/CVE-2024-28252/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28252 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28252 - OSV: https://osv.dev/vulnerability/CVE-2024-28252 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-28252/ Summaries are generated and may contain mistakes; the official description above is the record.