Netwrix Auditor User Activity Video Recording Remote Code Execution
CVE-2022-31199 is a critical unauthenticated remote code execution vulnerability in the Netwrix Auditor User Activity Video Recording (UAVR) component. The issue exists in the underlying .NET remoting protocol used by the UAVRServer service, exposed on TCP port 9004, and is caused by insecure deserialization of attacker-controlled .NET objects. A remote attacker can send a crafted serialized payload to the vulnerable endpoint without authentication or user interaction and trigger arbitrary code execution on the Netwrix Auditor server or affected agents installed on monitored systems. Successful exploitation results in code execution as NT AUTHORITY\SYSTEM. The content states the issue affects Netwrix Auditor versions earlier than 10.5 and has been observed exploited in the wild.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a comprehensive lab and exploit toolkit for CVE-2022-31199, a critical unauthenticated remote code execution vulnerability in Netwrix Auditor (<10.5) via insecure .NET Remoting deserialization. The structure includes: - A vulnerable server simulator (Python and C#/.NET versions) that mimics the Netwrix UAVRServer endpoint on TCP port 9004, with intentionally insecure deserialization settings (TypeFilterLevel=Full). - Exploit scripts in Python (exploit.py, test_exploit.py) and PowerShell (exploit.ps1) that can check for the vulnerability and deliver serialized payloads to achieve RCE. The Python scripts can use payloads generated by ysoserial.net, and the PowerShell script automates the full attack chain. - Dockerfiles and docker-compose files for easy lab deployment on Windows, Linux, and macOS, including both the vulnerable server and an attacker machine. - Detection rules (Snort, YARA) and a Nuclei template for automated detection and scanning. - Documentation and guides for both manual and automated exploitation, including example payloads and post-exploitation steps. The main attack vector is network-based, targeting the .NET Remoting service on TCP port 9004. The exploit achieves SYSTEM-level code execution by sending a malicious serialized object to the UAVRServer endpoint. The repository is well-structured for both educational and practical exploitation, with clear separation between vulnerable server code, exploit tools, detection signatures, and documentation.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical remote code execution vulnerability in Netwrix Auditor's User Activity Video Recording (UAVR) component, caused by insecure object deserialization in the .NET remoting protocol. Allows unauthenticated attackers to execute arbitrary code as SYSTEM, potentially compromising Active Directory environments.
A vulnerability in Netwrix Auditor used for initial access; linked to Truebot activity and later Clop ransomware operations.
Netwrix Auditor insecure deserialization enabling code execution.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.