wcfproxy

Build You can either compile the tool once and then use the resulting binary or you can run it "like a script" the Go toolchain will compile it on the fly. For development, the latter option is convenient. For productive use, it is recommended to compile it once from the cli directory and use the...

CVE-2025-66631

CSLA .NET is a framework designed for the development of reusable, object-oriented business layers for applications. Versions 5.5.4 and below allow the use of WcfProxy. WcfProxy uses the now-obsolete NetDataContractSerializer NDCS and is vulnerable to remote code execution during deserialization...

CVE-2025-66631 CSLA .NET is vulnerable to Remote Code Execution via WcfProxy

CSLA .NET is a framework designed for the development of reusable, object-oriented business layers for applications. Versions 5.5.4 and below allow the use of WcfProxy. WcfProxy uses the now-obsolete NetDataContractSerializer NDCS and is vulnerable to remote code execution during deserialization...

CVE-2025-66631

CSLA .NET prior to 6.0.0 is vulnerable to remote code execution during deserialization when using WcfProxy, which relies on the obsolete NetDataContractSerializer (NDCS). Supported details from multiple sources show that versions 5.5.4 and below are affected, while version 6.0.0 and above remove ...

Csla affected by Remote Code Execution via WcfProxy (NetDataContractSerializer)

Impact Versions of CSLA .NET prior to version 6 allow the use of WcfProxy. WcfProxy uses the NetDataContractSerializer NDCS which has known vulnerabilities that can allow remote execution of code during deserialization. NDCS itself is considered obsolete, and you should avoid using WcfProxy or...