# CVE-2024-51324: Privilege escalation in n/a

> Attackers can terminate arbitrary processes and escalate privileges via a vulnerable driver in Baidu Antivirus.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-prq3-r4gw-34vp

## What is CVE-2024-51324?

CVE-2024-51324 is a low-severity vulnerability in n/a, published on 11 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue in the BdApiUtil driver of Baidu Antivirus v5.2.3.116083 allows attackers to terminate arbitrary process via executing a BYOVD (Bring Your Own Vulnerable Driver) attack.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-51324?


## How do I fix CVE-2024-51324?

No fix has been published for CVE-2024-51324 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-51324 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51324 exists.

Public exploit code:

- Master's Thesis research on CVE-2024-51324 (BYOVD). Advanced exploit with 4 operational modes (SCANNER, LOADER, KILLER, CLEANUP), SHA-256 driver verification, and full academic documentation. Portfolio piece covers Windows kernel driver security, IOCTL reverse engineering, and Bring Your Own Vulnerable Driver exploitation. (github_poc): https://github.com/devianntsec/CVE-2024-51324
- C++ Windows research tool for studying the BdApiUtil64.sys vulnerable driver and CVE-2024-51324 (github_poc): https://github.com/uLl0a/bdapiutil-bydov

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51324 and fix it if it is affected.

What it is: CVE-2024-51324 is a low-severity vulnerability in n/a, published on 11 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51324 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-51324/ (Markdown: https://insights.sbomify.com/CVE-2024-51324/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-51324
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-51324
- OSV: https://osv.dev/vulnerability/CVE-2024-51324

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-51324/
Summaries are generated and may contain mistakes; the official description above is the record.