dbcve.org
Sinvr 3 Central Control ServerApplication · Siemens

CVE-2019-18339

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
A vulnerability has been identified in SiNVR/SiVMS Video Server (All versions < V5.0.0). The HTTP service (default port 5401/tcp) of the SiVMS/SiNVR Video Server contains an authentication bypass vulnerability, even when properly configured with enforced authentication. A remote attacker with network access to the Video Server could exploit this vulnerability to read the SiVMS/SiNVR users database, including the passwords of all users in obfuscated cleartext.

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

An authentication bypass vulnerability exists in the HTTP service (port 5401/tcp) of SiNVR/SiVMS Video Server for all versions prior to V5.0.0. Despite proper authentication configuration, remote attackers can bypass authentication mechanisms to access the user database containing passwords stored in obfuscated cleartext.

MitigationUpgrade SiNVR/SiVMS Video Server to version V5.0.0 or later to remediate the authentication bypass. After upgrading, verify user account integrity and consider password resets since the previous versions stored credentials in insecure obfuscated cleartext.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 SiNVR/SiVMS installation
    Check for SiNVR or SiVMS Video Server software on the system by reviewing installed programs, services, or process listings. Look for service names containing 'SiNVR' or 'SiVMS'.
    Affected if SiNVR 3 Central Control Server or SiNVR 3 Video Server software is present on the system
  2. Verify HTTP service on port 5401/tcp
    Run 'netstat -an | findstr 5401' or 'ss -tlnp | grep 5401' to check if the HTTP service is listening on port 5401/tcp. Confirm local binding status.
    Affected if Port 5401/tcp is open and listening, indicating the vulnerable HTTP service is active
  3. Determine installed version
    Review installation directories, service properties, or product documentation to identify the exact version of SiNVR/SiVMS Video Server. Compare against V5.0.0.
    Affected if The installed version is any version prior to V5.0.0, or the version cannot be determined but the software is present
  4. Check network exposure of the HTTP service
    Review firewall rules, network configuration, or binding settings to determine if port 5401/tcp is accessible from untrusted networks or the internet.
    Affected if Port 5401/tcp is accessible from remote systems beyond the local host or trusted internal network

If SiNVR 3 Central Control Server or SiNVR 3 Video Server is installed with the HTTP service on port 5401/tcp accessible and the version is below V5.0.0, the environment is affected by this authentication bypass 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SiNVR/SiVMS Video Server to version V5.0.0 or later to remediate the authentication bypass. After upgrading, verify user account integrity and consider password resets since the previous versions stored credentials in insecure obfuscated cleartext.

Recommended fix High confidence

V5.0.0 or later

  1. Identify the current version of the SiVMS/SiNVR Video Server installation
  2. Back up all configuration files, the users database, and any existing recordings or data
  3. Upgrade the SiVMS/SiNVR Video Server to version 5.0.0 or later
  4. After upgrade, verify that the HTTP service on port 5401/tcp now requires proper authentication
  5. Confirm that the users database is no longer accessible without authentication
  6. Test that enforced authentication settings are functioning correctly
Caveat Major version upgrade from v3 to v5 - review migration documentation for any configuration or compatibility changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sinvr 3 Central Control Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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