Advisory

GHSA-32jq-mv89-5rx7

Also known as: CVE-2024-28252

Summary

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

Details

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

Severity

High Basis: The source's own band: HIGH

Dates

Published
2024-03-15 19:20 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

CoreWCF.NetFramingBase

NuGet · All systems

Affected

  • introduced 1.4.0, fixed 1.4.2 (ecosystem)

Fixed versions

1.4.2

Fix

The export has no generic command for this ecosystem.

CoreWCF.NetFramingBase

NuGet · All systems

Affected

  • introduced 1.5.0, fixed 1.5.2 (ecosystem)

Fixed versions

1.5.2

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences