dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-34058

HIGH · 8.7 CVSS v4.0 Published 2025-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Hikvision Streaming Media Management Server v2.3.5 uses default credentials that allow remote attackers to authenticate and access restricted functionality. After authenticating with these credentials, an attacker can exploit an arbitrary file read vulnerability in the /systemLog/downFile.php endpoint via directory traversal in the fileName parameter. This exploit chain can enable unauthorized access to sensitive system files.

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 confidence

Hikvision Streaming Media Management Server v2.3.5 ships with default credentials that permit remote attackers to authenticate to the system. Once authenticated, attackers can exploit a directory traversal vulnerability in the /systemLog/downFile.php endpoint via the fileName parameter to read arbitrary files from the filesystem, potentially exposing sensitive configuration or system data.

MitigationImmediately change or disable default credentials and implement strict input validation with allowlist-based path sanitization on the fileName parameter in the downFile.php endpoint to prevent directory traversal attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of Hikvision Streaming Media Management Server
    Access the server's admin interface or check the application's about/version page. Typically found under System > System Info or by querying the web service endpoint. Alternatively, check the installation directory for version files or review the HTTP Server header if exposed.
    Affected if The installed version matches v2.3.5 specifically, as this version ships with default credentials.
  2. Verify if default credentials are still active
    Attempt to authenticate to the web interface using the known default credentials for this product (consult product documentation for the specific default username/password pairs). Common Hikvision defaults include admin/admin or admin/12345, though the exact defaults for v2.3.5 should be verified against release notes.
    Affected if Authentication succeeds with any default credential pair, indicating the system shipped with or still uses default credentials.
  3. Confirm the vulnerable endpoint is accessible
    Send an HTTP GET request to /systemLog/downFile.php on the affected server. For example: GET /systemLog/downFile.php?fileName=test.log. Check if the endpoint returns a response or error message indicating the file download functionality exists.
    Affected if The endpoint responds, indicating the vulnerable file download functionality is present and exposed.
  4. Test for directory traversal on the fileName parameter
    Send a crafted request such as GET /systemLog/downFile.php?fileName=../../../../etc/passwd (or a Windows equivalent) and observe if the response contains content from files outside the intended directory. A successful traversal would return system file contents.
    Affected if The application returns file contents from paths outside the intended log directory, confirming the directory traversal vulnerability is exploitable.
  5. Determine if the management interface is exposed to untrusted networks
    Review firewall rules, network ACLs, or reverse proxy configurations to determine if the Hikvision management port (typically 80/443 or a custom web port) is accessible from the internet or untrusted internal networks.
    Affected if The management interface is reachable from untrusted networks, enabling remote attackers to exploit both the default credential and directory traversal issues.

A user is affected if the Hikvision Streaming Media Management Server is version 2.3.5 (or retains default credentials), has the /systemLog/downFile.php endpoint exposed, and is accessible from a network where untrusted actors can reach it.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately change or disable default credentials and implement strict input validation with allowlist-based path sanitization on the fileName parameter in the downFile.php endpoint to prevent directory traversal attacks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34058 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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