CVE-2019-18341
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 · uneditedA 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) contains an authentication bypass vulnerability. A remote attacker with network access to the CCS server could exploit this vulnerability to read data from the EDIR directory (for example, the list of all configured stations).
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 confidenceThe SFTP service (port 22/tcp) in Control Center Server versions before V1.5.0 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to access the EDIR directory and read sensitive data such as configured station lists.
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 dataall versionsall versionsCVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the system is a Siemens Sinvr 3 Central Control Server or Video ServerLocate system inventory or software asset records to confirm the installed product name matches 'Siemens Sinvr 3 Central Control Server' or 'Siemens Sinvr 3 Video Server'Affected if The system is identified as either Siemens Sinvr 3 Central Control Server or Siemens Sinvr 3 Video Server
-
Determine the installed version of Control Center ServerCheck the software version reported in the application, installed programs list, or product documentation for Control Center ServerAffected if The installed version of Control Center Server is identified as before V1.5.0 (any version prior to V1.5.0)
-
Verify if SFTP service on port 22/tcp is enabledCheck running services or configured server roles to confirm whether the SFTP service is active on the systemAffected if SFTP service on port 22/tcp is enabled and running
-
Confirm network accessibility of port 22/tcpVerify from network configuration, firewall rules, or port scanning results that port 22/tcp is open and reachable from network perspectiveAffected if Port 22/tcp is accessible from network locations where untrusted users could connect
A system is affected if it runs Siemens Sinvr 3 (Central Control Server or Video Server) with Control Center Server version before V1.5.0 and has the SFTP service on port 22/tcp enabled and network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Control Center Server to version V1.5.0 or later to patch the SFTP authentication bypass. If immediate patching is not feasible, restrict network access to port 22/tcp via firewall rules or network segmentation as a compensating control.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-18341 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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