# CVE-2024-57394: Path traversal in n/a

> Attackers can restore malicious files to arbitrary paths, enabling DLL hijacking and privilege escalation in Qi-ANXIN Tianqing Endpoint Security.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-v4fw-ww7x-63fp

## What is CVE-2024-57394?

CVE-2024-57394 is a high-severity path traversal vulnerability in n/a, published on 21 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The quarantine - restore function in Qi-ANXIN Tianqing Endpoint Security Management System v10.0 allows user to restore a malicious file to an arbitrary file path. Attackers can write malicious DLL to system path and perform privilege escalation by leveraging Windows DLL hijacking vulnerabilities.

Weakness: CWE-73 (External Control of File Name or Path)

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

It affects 1 product.


Products: Qianxin Tianqing Endpoint Security Management System.

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

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

## Is CVE-2024-57394 being exploited?

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

Public exploit code:

- CVE-2024-57394 (github_poc): https://github.com/cwjchoi01/CVE-2024-57394

## Fix prompt for AI coding agents

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

What it is: CVE-2024-57394 is a high-severity path traversal vulnerability in n/a, published on 21 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57394 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-57394/ (Markdown: https://insights.sbomify.com/CVE-2024-57394/index.md)
```

## Sources

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

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