CVE-2024-28252

{"id": "CVE-2024-28252", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2024-03-15T19:15:07.210", "references": [{"url": "https://github.com/CoreWCF/CoreWCF/issues/1345", "source": "security-advisories@github.com"}, {"url": "https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-32jq-mv89-5rx7", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-404"}]}], "descriptions": [{"lang": "en", "value": "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.\n"}, {"lang": "es", "value": "CoreWCF es una adaptaci\u00f3n del lado de servicio de Windows Communication Foundation (WCF) a .NET Core. Si tiene un servicio CoreWCF basado en NetFraming, se podr\u00edan consumir recursos adicionales del sistema si las conexiones se dejan establecidas en lugar de cerrarlas o cancelarlas. Hay dos escenarios en los que esto puede suceder. Cuando un cliente establece una conexi\u00f3n con el servicio y no env\u00eda datos, el servicio esperar\u00e1 indefinidamente a que el cliente inicie el protocolo de enlace de sesi\u00f3n de NetFraming. Adem\u00e1s, una vez que un cliente ha establecido una sesi\u00f3n, si el cliente no env\u00eda ninguna solicitud durante el per\u00edodo de tiempo configurado en el enlace ReceiverTimeout, la conexi\u00f3n no se cierra correctamente como parte del aborto de la sesi\u00f3n. Los enlaces afectados por este comportamiento son NetTcpBinding, NetNamedPipeBinding y UnixDomainSocketBinding. S\u00f3lo NetTcpBinding tiene la capacidad de aceptar conexiones no locales. Las versiones actualmente compatibles de CoreWCF son v1.4.x y v1.5.x. La soluci\u00f3n se puede encontrar en v1.4.2 y v1.5.3 de los paquetes CoreWCF. Se recomienda a los usuarios que actualicen. No existen workarounds para este problema."}], "lastModified": "2024-03-21T20:15:08.050", "sourceIdentifier": "security-advisories@github.com"}