Skip to main content
Mallory
MediumPublic exploit

Arbitrary PPL Process Termination in Topaz Antifraud wsftprm.sys

IdentifiersCVE-2023-52271CWE-269

Topaz Antifraud wsftprm.sys version 2.0.0.0 contains a local kernel-driver vulnerability that allows a low-privileged attacker to send a crafted IOCTL to the driver and cause termination of arbitrary processes, including Protected Process Light (PPL) processes. Based on the provided content, the vulnerable condition is exposed through the driver's IOCTL interface and results in unauthorized security-sensitive kernel functionality being made available to unprivileged users. The issue has been publicly disclosed as CVE-2023-52271 and has been referenced in BYOVD tradecraft to disable security tooling.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation allows an attacker with low privileges on the host to kill arbitrary processes, including PPL-protected security processes that are normally resistant to termination from user mode. In practice, this enables defense evasion by disabling EDR, AV, and other security controls, and can facilitate follow-on malicious activity such as privilege abuse, persistence, credential theft, lateral movement, and ransomware deployment. The provided reporting specifically notes use of this driver in BYOVD operations to obtain kernel-level advantages and terminate security tools.

Mitigation

If you can’t patch tonight, do this now.

Block or deny loading of wsftprm.sys using Microsoft Defender Application Control, Windows vulnerable driver blocklist, HVCI/Memory Integrity, or equivalent kernel driver allowlisting controls. Restrict administrative pathways that permit driver installation/loading, monitor for suspicious driver loads and IOCTL activity, and alert on attempts to terminate protected security processes. Where business requirements permit, remove unused third-party drivers and minimize the kernel attack surface.

Remediation

Patch, then assume compromise.

Upgrade or remove the vulnerable wsftprm.sys 2.0.0.0 driver from affected systems. If a fixed vendor version is available, deploy it and ensure the vulnerable signed driver can no longer be loaded. Review and enforce Microsoft vulnerable driver block rules, WDAC/HVCI policies, and EDR controls to prevent loading of known-bad third-party kernel drivers. Hunt for the presence of wsftprm.sys and related driver-load events in environments where Topaz Antifraud is not expected.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
BYOVD-CVE-2023-52271-POCMaturityPoCVerified exploit

Repository contains a small Windows C++ proof-of-concept exploit for CVE-2023-52271 targeting the Warsaw driver wsftprm.sys (noted in README as version 2.0.0.0). Structure is minimal: README.md (description/links) and main.cpp (the exploit). main.cpp implements a local, driver-based process-killing tool: it enumerates running processes via Toolhelp32 APIs, matches against a hardcoded list of Microsoft Defender/Windows security process names, and for each match opens the device \\.\Warsaw_PM and sends DeviceIoControl with IOCTL 0x22201C. The input buffer is 1036 bytes with the target PID placed in the first 4 bytes, which is intended to trigger the vulnerable driver behavior to terminate even PPL-protected processes. The program loops once per second until interrupted (CTRL+C), making it suitable for repeatedly killing respawning security services. No network communication is present; the key fingerprintable artifacts are the driver device path (\\.\Warsaw_PM), the IOCTL code (0x22201C), and the targeted process name list.

victoniDisclosed Jan 21, 2026c++markdownlocal
EXPOSURE SURFACE

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.

VendorProductType
TopazevolutionAntifraudapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence4

Every observed campaign linking this CVE to a named adversary.

Associated malware5

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity11

Community discussion across Reddit, Mastodon, and other social sources.