dbcve.org
Sppa T3000 Ms3000 Migration ServerApplication · Siemens

CVE-2019-18324

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-18325, CVE-2019-18326, 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

The SPPA-T3000 MS3000 Migration Server contains a critical vulnerability allowing an attacker with network access to send specially crafted packets to port 5010/tcp, triggering a denial-of-service condition and potentially achieving remote code execution. This represents a severe security flaw in a process control system component that could allow complete system compromise.

MitigationRestrict network access to the MS3000 Migration Server and port 5010/tcp using network segmentation and firewall rules to prevent untrusted attackers from reaching the vulnerable service, as the attacker requires direct network connectivity to exploit this flaw.

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 SPPA-T3000 MS3000 Migration Server is installed
    Check for the presence of Siemens SPPA-T3000 software components on the system. Look for installation directories such as C:\Program Files\Siemens\SPPA-T3000 or /opt/siemens/sppa-t3000 on Linux systems. Check Windows Services or Linux service definitions for 'MS3000' or 'Migration Server' services.
    Affected if The MS3000 Migration Server software is present on the system
  2. Verify port 5010/tcp is listening
    Run command 'netstat -an | findstr 5010' on Windows or 'netstat -an | grep 5010' on Linux to check if port 5010 is in LISTENING state. Alternatively, use 'nmap -p 5010 localhost' or 'Test-NetConnection -ComputerName localhost -Port 5010' on Windows PowerShell.
    Affected if Port 5010/tcp is open and listening on any network interface (0.0.0.0 or actual IP addresses)
  3. Confirm the Migration Server service is running
    On Windows, open Services console (services.msc) and look for a service named 'MS3000 Migration Server' or similar. On Linux, check with 'systemctl status ms3000*' or 'ps aux | grep -i migration'.
    Affected if The MS3000 Migration Server service is running and port 5010/tcp is active
  4. Check network exposure of port 5010
    Determine if port 5010 is bound to non-loopback interfaces. Review firewall rules with 'netsh advfirewall firewall show rule name=all' on Windows or 'iptables -L -n' on Linux. Use external port scanning from another host: 'nmap -p 5010 <target_IP>' to verify accessibility from the network.
    Affected if Port 5010/tcp is accessible from network segments other than localhost/127.0.0.1

The environment is affected if the SPPA-T3000 MS3000 Migration Server software is installed AND port 5010/tcp is open and accessible from the network, 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 firewall rules to prevent untrusted attackers from reaching the vulnerable service, as the attacker requires direct network connectivity to exploit this flaw.

Fix this in Sppa T3000 Ms3000 Migration Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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