dbcve.org
Sinvr 3 Central Control ServerApplication · Siemens

CVE-2019-18340

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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), Control Center Server (CCS) (All versions >= V1.5.0), SiNVR/SiVMS Video Server (All versions < V5.0.0), SiNVR/SiVMS Video Server (All versions >= V5.0.0). Both the SiVMS/SiNVR Video Server and the Control Center Server (CCS) store user and device passwords by applying weak cryptography. A local attacker could exploit this vulnerability to extract the passwords from the user database and/or the device configuration files to conduct further attacks.

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

The Control Center Server (CCS) and SiNVR/SiVMS Video Server store user and device passwords using weak cryptographic methods, allowing a local attacker with database or file system access to extract plaintext passwords and conduct further attacks.

MitigationUpgrade to the fixed versions (CCS V1.5.0+ and SiVMS/SiNVR V5.0.0+) and migrate existing passwords to strong hashing algorithms (e.g., bcrypt, Argon2).

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Siemens Sinvr/SiVMS components
    Determine if Siemens Sinvr 3 Central Control Server or SiNVR/SiVMS Video Server is installed on the system. Check installed programs, services, or documentation for these products.
    Affected if Either Sinvr 3 Central Control Server or SiNVR/SiVMS Video Server is present (all versions are affected)
  2. Locate password storage locations
    Identify where user and device credentials are stored. This may be in a database file (such as SQLite, MySQL, or MSSQL), configuration files, or credential storage directories used by the CCS or Video Server.
    Affected if Password storage is found in accessible database or file system locations
  3. Inspect password storage format
    Examine the stored password data directly in the database or configuration files. Look at the password field values to determine if they appear as plaintext or use recognizable weak hash formats (e.g., short MD5/SHA1 strings, unsalted hashes).
    Affected if Passwords are stored in plaintext or use weak hashing algorithms without proper salting
  4. Verify cryptographic implementation
    If possible, examine the application code or configuration that handles password storage to identify the specific encryption or hashing method used for credential persistence.
    Affected if The implementation uses weak cryptographic methods such as plaintext storage, MD5, SHA1 without salt, or other known weak algorithms

A user is affected if Siemens Sinvr 3 Central Control Server or SiNVR/SiVMS Video Server is installed and passwords are stored using weak cryptographic methods such as plaintext or unsalted weak hashes accessible via database or file system access.

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 the fixed versions (CCS V1.5.0+ and SiVMS/SiNVR V5.0.0+) and migrate existing passwords to strong hashing algorithms (e.g., bcrypt, Argon2).

Fix this in Sinvr 3 Central Control Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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