CVE-2025-5159
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 was found in H3C SecCenter SMP-E1114P02 up to 20250513. It has been rated as problematic. This issue affects the function Download of the file /cfgFile/1/download. The manipulation of the argument Name leads to path traversal. The attack may be initiated 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 confidenceA path traversal vulnerability in H3C SecCenter SMP-E1114P02 allows remote attackers to manipulate the 'Name' argument in the /cfgFile/1/download function to access files outside the intended directory. The CVSS 7.5 score indicates significant risk from unauthorized file read access, potentially exposing sensitive system files, configurations, or credentials.
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 installationLocate the H3C SecCenter SMP-E1114P02 application in your environment. Check product documentation, installed software list, or network device inventory for this specific product.Affected if The system is running H3C SecCenter SMP-E1114P02 software.
-
Check installed software versionAccess the SMP management interface or check system information to determine the exact version number. Compare the version/build date against the affected range (20250513 or earlier).Affected if The installed version is H3C SecCenter SMP-E1114P02 with a version date on or before 20250513.
-
Verify vulnerable endpoint accessibilityCheck if the /cfgFile/1/download endpoint is exposed and accessible on the SMP web interface. This may require authentication depending on the deployment configuration.Affected if The /cfgFile/1/download endpoint is reachable (with or without authentication).
-
Test Name parameter for path traversalIf the endpoint is accessible, attempt a controlled request to /cfgFile/1/download with a benign path traversal sequence in the Name parameter (such as ../../etc/passwd or ../../windows/win.ini) to verify the vulnerability exists.Affected if The application accepts directory traversal sequences in the Name parameter and returns file contents outside the intended directory.
A system is affected if it runs H3C SecCenter SMP-E1114P02 version 20250513 or earlier and has the /cfgFile/1/download endpoint accessible, where the Name parameter permits directory traversal.
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 dataImplement strict input validation and sanitization on the 'Name' parameter, using allowlists and canonicalizing paths to prevent directory traversal sequences (../). Consider restricting the download function to authorized paths only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5159 — 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-5159 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