cve.bz

CVE-2024-28252 corewcf corewcf: Improper Resource Shutdown or Release

7.5 highEPSS 0.6%Fix available

High (7.5) in corewcf corewcf. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in CoreWCF.NetFramingBase 1.4.2, 1.5.2.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 49th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2024-08-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-404 Improper Resource Shutdown or Release
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-28252 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-28252?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-28252?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-28252 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
corewcf:corewcf1.4.1
corewcf:corewcf1.5.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-32jq-mv89-5rx7NuGetCoreWCF.NetFramingBase>=1.4.0 <1.4.21.4.2
GHSA-32jq-mv89-5rx7NuGetCoreWCF.NetFramingBase>=1.5.0 <1.5.21.5.2

Attack patterns (CAPEC)

  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON