Sppa T3000 Ms3000 Migration ServerApplication · Siemens

CVE-2019-18310

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 could trigger a Denial-of-Service condition by sending specifically crafted packets to port 7061/tcp. This vulnerability is independent from CVE-2019-18311. 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 Denial-of-Service vulnerability exists in the SPPA-T3000 MS3000 Migration Server where an attacker with network access can send specially crafted packets to port 7061/tcp, causing the service to become unavailable. The attack requires only network connectivity to the target system and does not require authentication.

MitigationRestrict network access to the MS3000 Migration Server, especially blocking port 7061/tcp from untrusted networks using firewalls or network segmentation. Implement monitoring for anomalous traffic on port 7061/tcp.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Review installed software or running services on the system. Look for Siemens SPPA-T3000 components, particularly the MS3000 Migration Server service.
    Affected if The MS3000 Migration Server software is present on the system.
  2. Verify port 7061/tcp is listening
    Run a port scan or check listening ports on the system using commands such as 'netstat -an | grep 7061' or 'ss -tlnp | grep 7061'.
    Affected if Port 7061/tcp is open and listening on the system.
  3. Confirm network accessibility of port 7061/tcp
    From an external system or from an untrusted network segment, attempt to reach port 7061/tcp on the target system. Review firewall rules to determine if port 7061/tcp is exposed to untrusted networks.
    Affected if Port 7061/tcp is accessible from network segments that include untrusted or external attackers.
  4. Test service availability on port 7061/tcp
    Attempt to connect to port 7061/tcp using a tool such as 'telnet <target> 7061' or 'nc -zv <target> 7061'. Observe whether the connection establishes or the service responds.
    Affected if The MS3000 Migration Server service is running and accepting connections on port 7061/tcp.

A system is affected if it runs the Siemens SPPA-T3000 MS3000 Migration Server with port 7061/tcp exposed and accessible from network locations where untrusted attackers can reach it.

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, especially blocking port 7061/tcp from untrusted networks using firewalls or network segmentation. Implement monitoring for anomalous traffic on port 7061/tcp.

Fix this in Sppa T3000 Ms3000 Migration Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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