dbcve.org
Sinvr 3 Central Control ServerApplication · Siemens

CVE-2019-18337

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 Control Center Server (CCS) (All versions < V1.5.0). The Control Center Server (CCS) contains an authentication bypass vulnerability in its XML-based communication protocol as provided by default on ports 5444/tcp and 5440/tcp. A remote attacker with network access to the CCS server could exploit this vulnerability to read the CCS 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

Control Center Server (CCS) contains an authentication bypass vulnerability in its XML-based communication protocol on default ports 5444/tcp and 5440/tcp. A remote attacker with network access can bypass authentication entirely and read the CCS user database, which stores passwords in obfuscated cleartext.

MitigationUpgrade Control Center Server to version V1.5.0 or later. Until upgraded, restrict network access to ports 5444/tcp and 5440/tcp to trusted IPs 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
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. Confirm Siemens Sinvr 3 installation
    Locate and identify Siemens Sinvr 3 Central Control Server or Video Server software on the system. Check installed programs or service list for 'Sinvr' or 'Control Center Server' entries.
    Affected if Siemens Sinvr 3 Central Control Server or Video Server is installed on the machine
  2. Identify listening ports
    Run 'netstat -an | findstr "5444 5440"' or 'ss -tlnp | grep -E "5444|5440"' to check if ports 5444/tcp and 5440/tcp are in LISTEN state.
    Affected if Ports 5444/tcp or 5440/tcp are open and listening on the system
  3. Verify network exposure
    Check firewall rules or perform a port scan from an external system to determine if ports 5444/tcp and 5440/tcp are accessible from untrusted network segments.
    Affected if Ports 5444/tcp or 5440/tcp are accessible from network locations outside the trusted perimeter
  4. Confirm XML protocol service is active
    Verify the CCS XML-based communication service is running. Check Windows services or process list for the Control Center Server service handling XML protocol on the affected ports.
    Affected if The Control Center Server service is running and accepting connections on ports 5444/tcp or 5440/tcp

A system is affected if Siemens Sinvr 3 Central Control Server or Video Server is installed with ports 5444/tcp or 5440/tcp open and accessible, allowing remote attackers to bypass authentication via the XML protocol.

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 Control Center Server to version V1.5.0 or later. Until upgraded, restrict network access to ports 5444/tcp and 5440/tcp to trusted IPs only.

Recommended fix High confidence

CCS V1.5.0 or later

  1. Identify the current version of Control Center Server (CCS) installed on the system
  2. Obtain version V1.5.0 or later of Control Center Server from the official Siemens support portal (cert-portal.siemens.com)
  3. Back up the current CCS configuration, database, and all user data
  4. Stop the CCS service to ensure no active connections during upgrade
  5. Install CCS version V1.5.0 or later following the Siemens upgrade documentation
  6. Restart the CCS service after installation completes
  7. Verify the service is listening on ports 5444/tcp and 5440/tcp with authentication required
  8. Confirm that the user database now requires proper authentication to access

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-18337 — 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-18337 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