CVE-2025-5160
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePath traversal vulnerability in H3C SecCenter SMP-E1114P02 allows remote attackers to manipulate the Name argument in the /packetCaptureStrategy/download function to access arbitrary files outside the intended directory. The vulnerability is exploitable remotely and a public exploit exists.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 20250513CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify H3C SecCenter SMP installationConfirm the target system is running H3C SecCenter SMP by checking the product name via the web interface banner, system information page, or by querying the HTTP server banner on ports 80/443Affected if The system is NOT running H3C SecCenter SMP - you are not affected
-
Determine installed versionLocate the SMP version number in the web interface (typically under System > About or Help > Version) or check the firmware/build file name if accessible. Compare against the affected version pattern 20250513 or earlierAffected if The installed version is GREATER than 20250513 (newer than May 13, 2025) - you are not affected. If version is 20250513 or earlier, or cannot be determined, proceed to next check
-
Verify vulnerable endpoint existsAttempt to access /packetCaptureStrategy/download via HTTP/HTTPS on the target. A 404 response indicates the endpoint may not exist. A 400/401 or different response suggests the endpoint is presentAffected if The endpoint /packetCaptureStrategy/download returns 404 or is unreachable - you are likely not affected
-
Test for path traversal in Name parameterSend a crafted request to /packetCaptureStrategy/download?Name=../etc/passwd or similar path traversal pattern. Check if the response contains content from outside the intended capture file directory (e.g., system files, configuration files)Affected if The application returns file contents from outside the intended directory (e.g., shows /etc/passwd or other system files) - you ARE affected
You are affected if the system is H3C SecCenter SMP version 20250513 or earlier AND the /packetCaptureStrategy/download endpoint is accessible AND path traversal in the Name parameter returns arbitrary file contents.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince the vendor did not respond, implement compensating controls such as WAF rules to block path traversal patterns in URLs, network segmentation to limit exposure, and input validation at upstream proxies if the application-level fix is unavailable.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5160 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5160 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data