Top 10 winner
Bypassing .NET Serialization Binders
A .NET SerializationBinder that validates type names as strings, or returns null when it cannot resolve one, can be bypassed: BinaryFormatter then falls back to its own resolver. An assembly-qualified name parsed differently by binder and runtime restores blocked gadget types, giving remote code execution in DevExpress (CVE-2022-28684) and Exchange (CVE-2022-23277).
In the archive
Tags
This page is the archive's own catalogue record. The research is the work of its author, first published at the original source. Preserved copies are kept so the citation survives its host.