dbcve.org
Sinvr 3 Central Control ServerApplication · Siemens

CVE-2019-19296

MEDIUM · 6.8 CVSS v3.1 Published 2020-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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 SiNVR/SiVMS Video Server (All versions < V5.0.0). The two FTP services (default ports 21/tcp and 5411/tcp) of the SiVMS/SiNVR Video Server contain a path traversal vulnerability that could allow an authenticated remote attacker to access and download arbitrary files from the server, if the FTP services are enabled.

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 · moderate confidence

The SiNVR/SiVMS Video Server contains a path traversal vulnerability in its FTP services (ports 21/tcp and 5411/tcp). An authenticated attacker can use directory traversal sequences (e.g., ../../../') in FTP commands to escape the intended directory and read arbitrary files on the server file system.

MitigationUpgrade to SiVMS/SiNVR version V5.0.0 or later. If the FTP services are not required, they should be disabled. If required, restrict network access to trusted authenticated users only.

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
Sinvr 3 Central Control ServerApplication
Affected:all versions
Sinvr 3 Video ServerApplication
Affected:all versions

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 checks

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

  1. Identify if Siemens Sinvr 3 is installed
    Check for SiNVR or SiVMS installation directories, services, or software listings. Common paths may include C:\Program Files\Siemens\Sinvr or C:\Program Files\SiVMS. On Linux, check /opt/sinvr or /opt/sivms. Look for Siemens software in Windows Registry or system services.
    Affected if SiNVR 3 or SiVMS version 3.x is present on the system
  2. Verify the installed version
    Check the version of the installed SiNVR/SiVMS software. Look in the software itself (Help > About), check installation directories for version files, or use system commands to query installed software versions.
    Affected if The version is 3.x (any version of Sinvr 3 Central Control Server or Sinvr 3 Video Server, since all versions are affected)
  3. Check if FTP service is running on port 21/tcp
    Use netstat, ss, or a port scanner to verify if the system is listening on TCP port 21. Commands: netstat -an | findstr :21, ss -tlnp | grep :21, or nmap -p 21 <target>
    Affected if FTP service is listening on port 21/tcp on the SiNVR/SiVMS server
  4. Check if FTP service is running on port 5411/tcp
    Use netstat, ss, or a port scanner to verify if the system is listening on TCP port 5411 (the alternate SiNVR FTP port). Commands: netstat -an | findstr :5411, ss -tlnp | grep 5411, or nmap -p 5411 <target>
    Affected if FTP service is listening on port 5411/tcp on the SiNVR/SiVMS server
  5. Assess network accessibility of FTP services
    Determine if the FTP ports (21/tcp and 5411/tcp) are exposed to untrusted networks. Check firewall rules, NAT configurations, and network segmentation. Attempt a connection from an untrusted network segment if authorized.
    Affected if FTP ports are accessible from untrusted networks or the internet without proper access controls

If Siemens Sinvr 3 or SiVMS version 3.x is installed AND the FTP service on port 21/tcp or 5411/tcp is running and accessible, the environment is affected by this path traversal vulnerability.

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

Upgrade to SiVMS/SiNVR version V5.0.0 or later. If the FTP services are not required, they should be disabled. If required, restrict network access to trusted authenticated users only.

Fix this in Sinvr 3 Central Control Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19296 — 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-2019-19296 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