1-minute read
What a defender needs to know
Some WSUS deployments can be turned into targeted unsigned-payload distributors when SUSDB runs on a separate Microsoft SQL Server. SpecterOps demonstrated coercing the WSUS server’s computer account, relaying its NTLM authentication to that database, then using the account’s permitted WSUS stored procedures to construct and deploy a forged update.
The chain is not a universal internet RCE and has not been reported as exploited in the wild. The attacker needs network position for NTLM coercion and relay, reachability to the separate SQL server, and a deployment that accepts the relayed authentication.
The critical bypass sits in Microsoft.UpdateServices.ContentSyncAgent.dll: payload filenames ending in .txt or .esd skip certificate-signature validation. The command-line update handler can still execute the file. In the lab, Ghost.txt reached a workstation and called back; a failed update also redeployed, and automatic-install Group Policy can remove user interaction.
Inventory WSUS by database architecture. For every standalone SUSDB, require Extended Protection for Authentication where compatible and restrict SQL access to authorized WSUS and management hosts. Audit stored-procedure use, target groups, content URLs, deployed files, signer state, and client execution. Confirm update synchronization, approval, download, and deployment still work after the control change, then compare WSUS, SQL, BITS, Windows Update, and endpoint process records across the plausible relay window for forged .txt or .esd delivery to clients and servers.
EPA fixes the relay path going forward. It does not rewrite the update history that clients already accepted from WSUS.