CVE-2019-18311
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 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-18310. 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 · high confidenceA Denial-of-Service vulnerability in the SPPA-T3000 MS3000 Migration Server allows remote attackers with network access to crash the service by sending specifically crafted packets to port 7061/tcp. This is a network-layer DoS affecting a critical industrial control system component.
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 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SPPA-T3000 MS3000 Migration Server is installedReview installed software listings or check for the presence of Siemens SPPA-T3000 Migration Server components on the system. Look for processes named 'MS3000' or related migration server executables in process lists.Affected if The SPPA-T3000 MS3000 Migration Server software is present and running on the system
-
Verify if port 7061/tcp is listeningRun a port scan or use netstat/ss commands to check if port 7061/tcp is open and listening on any network interface (e.g., 'netstat -an | grep 7061' or 'ss -tlnp | grep 7061').Affected if Port 7061/tcp is open and accepting connections on the system
-
Check network exposure of port 7061Review firewall rules and network configurations to determine if port 7061/tcp is accessible from external or untrusted network segments. Check if the listening port is bound to non-loopback interfaces.Affected if Port 7061/tcp is accessible from network segments outside the trusted management zone
-
Confirm service availability on the networkAttempt to verify connectivity to port 7061/tcp from an external perspective using network scanning tools, or review network boundary device logs for traffic to port 7061.Affected if The service on port 7061/tcp responds to network requests from untrusted sources
The environment is affected if the SPPA-T3000 MS3000 Migration Server is running with port 7061/tcp exposed to network segments that are not strictly controlled.
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 dataRestrict network access to port 7061/tcp using firewalls or network segmentation to limit exposure to trusted systems only; implement monitoring for anomalous traffic patterns to port 7061/tcp.
- 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-18311 — 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-18311 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