Sinec Network Management SystemApplication · Siemens

CVE-2020-25237

HIGH · 8.1 CVSS v3.1 Published 2021-02-09
Fix available
A fix is available. Upgrade to 1.0 / 14.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
A vulnerability has been identified in SINEC NMS (All versions < V1.0 SP1 Update 1), SINEMA Server (All versions < V14.0 SP2 Update 2). When uploading files to an affected system using a zip container, the system does not correctly check if the relative file path of the extracted files is still within the intended target directory. With this an attacker could create or overwrite arbitrary files on an affected system. This type of vulnerability is also known as 'Zip-Slip'. (ZDI-CAN-12054)

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

This is a Zip-Slip vulnerability (directory traversal) in SINEC NMS and SINEMA Server file upload functionality. When processing zip archives, the system fails to validate that extracted file paths remain within the intended target directory, allowing attackers to use '../' path traversal sequences in filenames to write files to arbitrary locations on the system.

MitigationUpdate to SINEC NMS V1.0 SP1 Update 1 or SINEMA Server V14.0 SP2 Update 2. Until patched, disable or restrict zip file upload functionality where possible.

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
Sinec Network Management SystemApplication
Affected:< 1.0= 1.0
Sinema ServerApplication
Affected:< 14.0= 14.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

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 product
    Determine whether the system has Siemens SINEC Network Management System or Siemens SINEMA Server installed. Check installed programs, services, or documentation that lists the deployed Siemens management software.
    Affected if The system has either SINEC NMS or SINEMA Server installed and the version is unpatched
  2. Determine the installed version of SINEC NMS
    Use the system's software inventory or version check mechanism to obtain the exact version number of SINEC Network Management System. Compare against the affected range: versions < 1.0 and version 1.0.
    Affected if The installed version is 1.0 or earlier (less than 1.0 or exactly 1.0)
  3. Determine the installed version of SINEMA Server
    Use the system's software inventory or version check mechanism to obtain the exact version number of SINEMA Server. Compare against the affected range: versions < 14.0 and version 14.0.
    Affected if The installed version is 14.0 or earlier (less than 14.0 or exactly 14.0)
  4. Verify file upload feature accessibility
    Determine whether the web-based file upload functionality in the management interface is exposed and accessible to users. This may involve checking web server configurations, service bindings, or access control settings.
    Affected if The file upload interface is exposed and users with upload permissions can submit files to the system

A user is affected if the system runs SINEC NMS version 1.0 or earlier, or SINEMA Server version 14.0 or earlier, AND the file upload feature is accessible to authenticated users.

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
Upgrade available Upgrade to 1.0 / 14.0 or later
Fixed in 1.014.0
Interim mitigation

Update to SINEC NMS V1.0 SP1 Update 1 or SINEMA Server V14.0 SP2 Update 2. Until patched, disable or restrict zip file upload functionality where possible.

Fix this in Sinec Network Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25237 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-25237 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