Of Course We Built a WSUS Ludus Lab

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

TL;DR: This blog walks you through setting up a WSUS lab using Ludus for testing.

The associated GitHub repo is here.

Introduction

I have been researching the Windows Service Update Service (WSUS) and discovered a new way we could take over the WSUS infrastructure and deploy custom payloads for lateral movement. As part of this research, I created a Ludus lab to help automate the lab deployment for testing.

The series can be found here:

Turning Enterprise Update Servers Into Backdoor Factories (0_o) – Part 1

Turning Enterprise Update Servers Into Backdoor Factories (0_o) – Part 2

Erik Hunstad developed Ludus which simplifies lab deployments in a virtual environment and I definitely recommend checking out: Ludus

Roles

Ludus uses Ansible roles to manage the software and configurations in the lab environment. The following are roles that I created for this lab.

ludus_wsus_install_wsus_server

This role installs the WSUS role on a server and configures the WSUS server. This also configures WSUS to user an external MSSQL server.

This role requires the ludus_wsus_sql_server_fqdn variable to be specified in the Ludus configuration file to specify the fully qualified domain name of the external SQL server.

ludus_wsus_sql

This downloads and installs SQL Server Management Studio (SSMS), creates a SQL service account and installs a SQL server.

The SQL server is configured to run as the created service account and the default Ludus domainadmin account is configured to have database admin permissions.

ludus_wsus_configure_client_gpo

This role creates a group policy …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://specterops.io/blog/2026/08/05/built-a-wsus-ludus-lab/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.