dbcve.org
Control Center ServerApplication · Siemens

CVE-2019-18342

CRITICAL · 9.9 CVSS v3.1 Published 2019-12-12
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Control Center Server (CCS) (All versions < V1.5.0). The SFTP service (default port 22/tcp) of the Control Center Server (CCS) does not properly limit its capabilities to the specified purpose. In conjunction with CVE-2019-18341, an unauthenticated remote attacker with network access to the CCS server could exploit this vulnerability to read or delete arbitrary files, or access other resources on the same server.

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 SFTP service in Control Center Server (CCS) versions before V1.5.0 has improper access control that allows the service to access files outside its intended scope. Combined with CVE-2019-18341 (authentication bypass), an unauthenticated remote attacker can read or delete arbitrary files on the server.

MitigationUpgrade Control Center Server to version V1.5.0 or later to remediate this vulnerability. If immediate upgrade is not possible, disable the SFTP service (port 22/tcp) and implement network segmentation to restrict access.

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
Control Center ServerApplication
Affected:< 1.5.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 Siemens Control Center Server installation
    Locate the Control Center Server installation directory or check installed programs list for Siemens CCS
    Affected if Control Center Server is installed on the system
  2. Check CCS version
    Use the product's built-in version information (typically via About dialog, registry, or version file in installation directory)
    Affected if Installed version is any release prior to V1.5.0 (e.g., V1.4.x, V1.3.x, etc.)
  3. Verify SFTP service status
    Check if the SFTP service is enabled and running in Windows Services or via command: sc query or Get-Service for the CCS SFTP service
    Affected if SFTP service is installed and currently running
  4. Check SFTP port accessibility
    Scan port 22/tcp or check firewall rules: netsh advfirewall firewall show rule name=all or netstat -an | findstr :22
    Affected if Port 22/tcp is open and accessible from network

User is affected if Siemens Control Center Server version is below V1.5.0 AND the SFTP service is enabled and accessible on the network.

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
Upgrade available Upgrade to 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Upgrade Control Center Server to version V1.5.0 or later to remediate this vulnerability. If immediate upgrade is not possible, disable the SFTP service (port 22/tcp) and implement network segmentation to restrict access.

Recommended fix High confidence

V1.5.0

  1. 1. Back up the current Control Center Server installation and configuration
  2. 2. Download Control Center Server version 1.5.0 or later from the Siemens cert-portal or official support channels
  3. 3. Stop the CCS service before performing the upgrade
  4. 4. Follow Siemens official upgrade/installation documentation to install version 1.5.0
  5. 5. After installation, verify the SFTP service configuration to ensure proper capability limitations are in place
  6. 6. Restart the CCS service and confirm normal operation
  7. 7. Verify the vulnerability is resolved by checking that the SFTP service no longer allows unauthorized file access

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

Fix this in Control Center Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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