Skip to main content
Mallory
LowPublic exploitVulnerability

CVE-2024-51324: Arbitrary Process Termination in Baidu Antivirus BdApiUtil Driver

Published Feb 11, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS3.8Low · v3.1
EPSS0.48%42nd percentile
CISA KEVNoNot listed
In the wildReported9 exploitation records in Mallory
IdentifiersCVE-2024-51324CWE-269 · Improper Privilege Management

CVE-2024-51324 is an improper privilege management vulnerability in the BdApiUtil kernel driver associated with Baidu Antivirus v5.2.3.116083. It allows a local attacker to terminate arbitrary processes, including protected endpoint security processes, by abusing privileged driver functionality. Attackers have exploited the vulnerability through Bring Your Own Vulnerable Driver (BYOVD) techniques in DeadLock and GOLD SALEM ransomware operations. A related driver process-termination interface accepts IOCTL 0x800024B4 with a four-byte process identifier and reaches ZwTerminateProcess; attribution of separately analyzed driver version 4.6.1.65082 to this CVE remains qualified because its version differs from the identified antivirus product version.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can disrupt applications and services and disable antivirus or endpoint detection and response processes. Terminating security agents impairs monitoring and prevention, facilitating subsequent malicious activity, including ransomware deployment. The demonstrated primitive is privileged process termination, not arbitrary kernel code execution.

Mitigation

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

Apply compatible vulnerable-driver controls, including Microsoft's vulnerable-driver blocklist and explicit WDAC or App Control policies targeting the affected driver. Enable the Microsoft Defender ASR rule for abused vulnerable signed drivers and Core Isolation Memory Integrity where supported and compatible. Restrict driver installation and loading to authorized administrators, inventory existing vulnerable drivers, and monitor unexpected driver-service creation followed by termination of security processes.

Remediation

Patch, then assume compromise.

A vendor-confirmed fixed version or patch is currently not available in the supplied information. Remove the affected driver from systems where it is unnecessary, and obtain vendor confirmation of a corrected release before retaining or redeploying it.

Public exploits

Exploits

3 exploits validated by Mallory's analysis.

View more in app →
CVE-2024-51324This repository is a real local BYOVD exploit/research project for CVE-2024-51324 affecting Baidu Antivirus/BdApiUtil64.sys on Windows. The main exploit code is exploit/byovd_killer.py, a Python script using ctypes and standard Windows APIs. It is not part of a common exploit framework. The repository also contains extensive reverse-engineering notes and defensive detections (Sigma and Sysmon). Primary exploit capability: the script operationalizes the driver’s exposed process-kill primitive by opening the user-accessible device \\.\BdApiUtil and sending IOCTL 0x800024B4 with a target PID. The documentation explains that the underlying driver lacks access control on its device object and internally uses PsLookupProcessByProcessId plus ObOpenObjectByPointer(KernelMode), bypassing normal SeAccessCheck logic. As a result, once the vulnerable signed driver has been loaded into the kernel by an administrator, subsequent exploitation can be performed by any local user to terminate arbitrary non-PPL processes. This is suitable for defense evasion, such as killing EDR/AV processes. The included exploit implements four modes: SCANNER (system/driver/process reconnaissance), LOADER (create/start kernel service for the vulnerable driver), KILLER (terminate by process name or PID, with max-instance and dry-run options), and CLEANUP (stop/delete the service and unload the driver). It verifies the driver by SHA-256 before loading. The exploit explanation states it searches for BdApiUtil64.sys in several local paths including drivers/, current directory, Python executable directory, %TEMP%, C:\Windows\Temp, and C:\Users\Public\Downloads. Although the Python exploit mainly weaponizes process termination, the repository’s analysis documents two additional vulnerable driver primitives: IOCTL 0x80002648 for arbitrary file deletion and IOCTL 0x8000264C for deletion of in-use files by temporarily nulling SectionObjectPointer fields. Those capabilities are described in the research docs but are not clearly implemented in the provided Python entry point. Repository structure: README.md provides overview and usage; docs/analysis/*.md contains root-cause analysis, reverse engineering details, and timeline; docs/detection/ contains Sigma and Sysmon detection content keyed to service creation, driver load, hash, and registry artifacts; exploit/byovd_killer.py is the main executable; exploit/exploit-explanation.md documents CLI usage and architecture. Overall, this is an operational local Windows exploit plus research/detection package, not merely a detector or README-only PoC.devianntsec · Disclosed Mar 25, 2026 · python · yaml · local · fileOperationalCVE-2024-51324-BYOVD-Masters-ThesisThis repository is a real local Windows BYOVD exploit and accompanying research package for CVE-2024-51324 in Baidu Antivirus's signed kernel driver BdApiUtil64.sys. The repository contains 7 files total, with one primary code file: exploit/byovd_killer.py. The remaining files are documentation: a top-level README, an exploit usage guide, and three analysis documents covering root cause, reverse engineering findings, and disclosure timeline. The main exploit capability is arbitrary process termination through a vulnerable device interface exposed by the driver. The exploit targets the user-accessible device path \\.\BdApiUtil, which maps to \Device\BdApiUtil / \DosDevices\BdApiUtil in kernel space. It sends a 4-byte PID to IOCTL 0x800024B4 using DeviceIoControl. According to the included analysis, the driver performs no authorization checks before calling ZwOpenProcess(PROCESS_TERMINATE) and ZwTerminateProcess, allowing any local user to kill many elevated or security-relevant processes once the driver is loaded. The exploit is therefore primarily a defense-evasion / process-kill primitive rather than a full privilege-escalation exploit. PPL-protected processes may resist termination. The Python tool is structured as a multi-mode utility with four operational modes: SCANNER (enumerates system/driver status and optionally searches for a target process), LOADER (loads the vulnerable driver into the kernel via Windows service creation), KILLER (terminates processes by name or PID through the vulnerable IOCTL), and CLEANUP (stops the service and unloads/removes the driver). The code also includes driver discovery across multiple filesystem paths, SHA-256 verification of the expected vulnerable driver, admin checks for load/unload operations, and CLI argument parsing. The documented expected hash is 47EC51B5F0EDE1E70BD66F3F0152F9EB536D534565DBB7FCC3A05F542DBE4428. No external C2 or remote network infrastructure is present; this is a local-only exploit. Fingerprintable artifacts are mostly host-based: the device path \\.\BdApiUtil, the driver filename BdApiUtil64.sys, the likely service registry path under HKLM\SYSTEM\CurrentControlSet\Services\<service_name>, and the documented search paths such as drivers/, %TEMP%, C:\Windows\Temp, and C:\Users\Public\Downloads. The repository also documents additional IOCTLs discovered during reverse engineering (0x800024B0, 0x800024B8, 0x800024BC), though the exploit’s core offensive action centers on 0x800024B4. Overall, this is an operational proof-of-concept exploit with practical local post-compromise utility: an operator with admin rights can load the signed vulnerable driver, after which even a standard user context can use the exposed device to terminate selected processes. The repository’s purpose is both exploitation and academic documentation of the vulnerability, with strong emphasis on reverse engineering, BYOVD tradecraft, and defender guidance.devianntsec · Disclosed Mar 25, 2026 · python · markdown · local · kernel driver / BYOVDOperationalbdapiutil-bydovThis four-file C++/CMake repository builds BdApiKiller, a local Windows bring-your-own-vulnerable-driver (BYOVD) utility targeting CVE-2024-51324 in BdApiUtil64.sys. The sole implementation, main.cpp, accepts a target executable name through a positional argument, -n, or --name; enumerates running processes with the Tool Help API; and obtains the first case-insensitive matching PID. It opens the named kernel device \\.\BdApiUtil with read/write access and issues IOCTL 0x800024B4 with the PID as its input buffer. It reports common IOCTL errors and validates the apparent result by attempting to open/wait on the target process after a short delay. The project links advapi32 and is configured for C++17/MSVC. README.md documents Windows 10/11 x64, a loaded BdApiUtil64.sys driver, and likely administrative privileges as prerequisites. No network activity, remote endpoint, shell payload, persistence, driver installation, or driver delivery mechanism is present; the utility relies on a pre-existing loaded vulnerable driver.uLl0a · Disclosed Sep 13, 2026 · c++ · cmake · localOperational
FAQ

Frequently asked questions

Is CVE-2024-51324 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2024-51324?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2024-51324, the earliest disclosed Mar 25, 2026.
Is there a patch for CVE-2024-51324?
A vendor-confirmed fixed version or patch is currently not available in the supplied information. Remove the affected driver from systems where it is unnecessary, and obtain vendor confirmation of a corrected release before retaining or redeploying it.
How severe is CVE-2024-51324?
CVE-2024-51324 has a CVSS v3.1 score of 3.8 (Low) and an EPSS score of 0.48% (42nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
malware newsNews · Oct 6, 2026IronChain Ransomware Threatens Businesses with Permanent Data Loss and Costly Downtime - Malware News - Malware Analysis, News and IndicatorsA Baidu Antivirus driver vulnerability referenced alongside IronChain’s coherent BdApiUtil.sys process-termination implementation. The bundled driver accepts IOCTL 0x800024B4 with a four-byte PID and reaches ZwTerminateProcess. However, applicability of this specific CVE to the bundled driver is uncertain, and successful runtime exploitation is not established.Read more ↗anyrun blogNews · Oct 6, 2026IronChain Ransomware Raises Business Data Loss RiskA vulnerability referenced in connection with Baidu's BdApiUtil driver. IronChain implements a coherent kernel-level process-termination path using bundled BdApiUtil.sys 4.6.1.65082, but the article cautions that attribution of this exact driver to the CVE is uncertain. Successful runtime exploitation is not established.Read more ↗reliaquest com threat huntingNews · Jul 16, 2026Ransomware and Cyber Extortion in Q2 2026An improper privilege management vulnerability in a legitimate but vulnerable signed antivirus driver that Deadlock abuses in a Bring Your Own Vulnerable Driver (BYOVD) chain to terminate protected EDR processes at kernel level before ransomware encryption.Read more ↗sdsgNews · Mar 22, 2026ESETの公開した90種類以上のEDR Killerを調査した記事を読んで思ったこと - Slapdash SafeguardsA vulnerability in the Baidu Antivirus driver BdApiUtil.sys that enables kernel-level process termination in BYOVD attacks and was reportedly used by DeadLock ransomware tooling.Read more ↗
+8 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence3Every report linking this CVE to a named adversary.
Associated malware6Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity13Community discussion across Reddit, Mastodon, and other social sources.