Sppa T3000 Ms3000 Migration ServerApplication · Siemens

CVE-2019-18326

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 SPPA-T3000 MS3000 Migration Server (All versions). An attacker with network access to the MS3000 Server can cause a Denial-of-Service condition and potentially gain remote code execution by sending specifically crafted packets to 5010/tcp. This vulnerability is independent from CVE-2019-18323, CVE-2019-18324, CVE-2019-18325, CVE-2019-18327, CVE-2019-18328, CVE-2019-18329, and CVE-2019-18330. Please note that an attacker needs to have network access to the MS3000 in order to exploit this vulnerability. At the time of advisory publication no public exploitation of this security vulnerability was known.

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 confidence

A critical vulnerability in the SPPA-T3000 MS3000 Migration Server allows an attacker with network access to send specially crafted packets to port 5010/tcp, causing denial of service and potentially achieving remote code execution on the affected server.

MitigationRestrict network access to the MS3000 Migration Server and port 5010/tcp using network segmentation and firewalls; implement compensating controls such as intrusion detection monitoring for the identified attack pattern.

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
Sppa T3000 Ms3000 Migration 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. Identify if MS3000 Migration Server is installed
    Check system inventory or installed software list for Siemens SPPA-T3000 MS3000 Migration Server component. On Windows, review Add/Remove Programs or check for installation directories related to Siemens Sppa T3000.
    Affected if The MS3000 Migration Server component is present on the system
  2. Verify if port 5010/tcp is listening
    Run 'netstat -an | findstr :5010' or 'ss -tlnp | grep 5010' to check if port 5010 is in LISTEN state. Alternatively, use a port scanner from an external location to test TCP connectivity to port 5010.
    Affected if Port 5010/tcp is open and accepting connections
  3. Determine network exposure of the service
    Check firewall rules or network segmentation configuration to determine if port 5010 is accessible from untrusted networks. Review inbound rules on host-based firewalls and network perimeter devices.
    Affected if Port 5010 is accessible from network segments outside the trusted control network
  4. Confirm service is reachable without authentication
    Attempt a TCP connection to port 5010 from a non-privileged network position to verify the service responds to unauthenticated packets.
    Affected if The service accepts connections on port 5010 without requiring authentication credentials

You are affected if the MS3000 Migration Server is installed and port 5010/tcp is exposed to accessible network segments, since all versions of this product are vulnerable.

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

Restrict network access to the MS3000 Migration Server and port 5010/tcp using network segmentation and firewalls; implement compensating controls such as intrusion detection monitoring for the identified attack pattern.

Fix this in Sppa T3000 Ms3000 Migration Server Scoped from the published advisory
  • Consultation30.0 h
  • Implementation40.0 h
  • Testing25.0 h
  • Review / QA15.0 h
110.0 hours of engineering $19,650
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-18326 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