# CVE-2025-5160: H3C SecCenter SMP-E1114P02 download path traversal

> Remote attackers can exploit a path traversal vulnerability in the download function to read arbitrary files from the H3C SecCenter SMP system.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 26 May 2025
- **Updated:** 28 May 2025
- **Also known as:** GHSA-4558-4wr6-c38x

## What is CVE-2025-5160?

CVE-2025-5160 is a medium-severity path traversal vulnerability in H3C SecCenter SMP-E1114P02, published on 26 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in H3C SecCenter SMP-E1114P02 up to 20250513. Affected is the function Download of the file /packetCaptureStrategy/download. The manipulation of the argument Name leads to path traversal. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-5160?

It affects 1 product.


Products: H3c Seccenter Smp-1114p02.

## How do I fix CVE-2025-5160?

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

## Is CVE-2025-5160 being exploited?

There is no known exploitation of CVE-2025-5160 in the wild and no public exploit code.

## Other vulnerabilities in H3C SecCenter SMP-E1114P02

- [CVE-2025-5161](https://insights.sbomify.com/CVE-2025-5161/): H3C SecCenter SMP-E1114P02 download operationDailyOut path traversal (medium 5.3)
- [CVE-2025-5162](https://insights.sbomify.com/CVE-2025-5162/): H3C SecCenter SMP-E1114P02 importFile unrestricted upload (medium 5.3)
- [CVE-2025-5157](https://insights.sbomify.com/CVE-2025-5157/): H3C SecCenter SMP-E1114P02 fileContent path traversal (medium 5.3)
- [CVE-2025-5158](https://insights.sbomify.com/CVE-2025-5158/): H3C SecCenter SMP-E1114P02 downloadSoftware path traversal (medium 5.3)
- [CVE-2025-5159](https://insights.sbomify.com/CVE-2025-5159/): H3C SecCenter SMP-E1114P02 download path traversal (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5160 and fix it if it is affected.

What it is: CVE-2025-5160 is a medium-severity path traversal vulnerability in H3C SecCenter SMP-E1114P02, published on 26 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5160 in the wild and no public exploit code.

Affected product: H3C SecCenter SMP-E1114P02. 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-2025-5160/ (Markdown: https://insights.sbomify.com/CVE-2025-5160/index.md)
```

## Sources

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

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