CVE-2019-18338
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 Control Center Server (CCS) contains a directory traversal vulnerability in its XML-based communication protocol as provided by default on ports 5444/tcp and 5440/tcp. An authenticated remote attacker with network access to the CCS server could exploit this vulnerability to list arbitrary directories or read files outside of the CCS application context.
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 confidenceA directory traversal vulnerability exists in Control Center Server (CCS) versions below V1.5.0 in its XML-based communication protocol on ports 5440/tcp and 5444/tcp. An authenticated remote attacker with network access can exploit this to read files and list directories outside the CCS application context.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Siemens Sinvr 3 product versionLocate the installed Control Center Server or Video Server version through the product's about dialog, installation directory documentation, or Windows Programs and Features. Common paths include C:\Program Files\Siemens\Sinvr3\ or check registry under HKLM\Software\Siemens\Sinvr3.Affected if The installed version is below V1.5.0 (including all versions of Siemens Sinvr 3 Central Control Server and Siemens Sinvr 3 Video Server)
-
Verify ports 5440/tcp and 5444/tcp are listeningRun netstat -an | findstr "5440" or use a port scanner to confirm the XML-based communication protocol ports are in LISTENING state on the server.Affected if Either port 5440/tcp or 5444/tcp is open and listening (indicates the vulnerable protocol is active)
-
Confirm network exposure of vulnerable portsUse nmap, PowerShell Test-NetConnection, or verify firewall rules to determine if ports 5440/tcp and 5444/tcp are accessible from network addresses other than localhost/127.0.0.1.Affected if The ports are accessible from network hosts (not restricted to localhost only), which enables remote authenticated attackers to reach the vulnerable service
You are affected if you have any Siemens Sinvr 3 Central Control Server or Video Server installation below V1.5.0 with ports 5440/tcp or 5444/tcp open and reachable from your network.
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. Additionally, restrict network access to ports 5440/tcp and 5444/tcp to only authorized personnel.
- 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-18338 — 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-18338 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