CVE-2019-18330
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 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-18326, CVE-2019-18327, CVE-2019-18328, and CVE-2019-18329. 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 critical vulnerability exists in the SPPA-T3000 MS3000 Migration Server across all versions. Attackers with network access can send specially crafted packets to port 5010/tcp to cause denial of service and potentially achieve remote code execution. The vulnerability affects the migration server component which handles data migration tasks in the SPPA-T3000 industrial control system.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SPPA-T3000 MS3000 Migration Server installationCheck system inventory or installed software for Siemens SPPA-T3000 MS3000 Migration Server component. Look for Siemens automation software related to SPPA-T3000 systems.Affected if The MS3000 Migration Server component is installed on the system.
-
Verify if port 5010/tcp is listeningUse network scanning tools such as 'netstat -an | grep 5010' or 'nmap -p 5010 localhost' to determine if port 5010/tcp is open and listening on the target system.Affected if Port 5010/tcp is open and listening, indicating the migration server is active.
-
Confirm migration server service statusCheck for running processes or services associated with the MS3000 Migration Server component. On Windows, review services list; on Linux, check for migration-related processes.Affected if The migration server service or process is running on the host.
-
Assess network accessibility of port 5010From an external network perspective, test connectivity to port 5010/tcp using tools like 'telnet <target> 5010', 'nc -zv <target> 5010', or port scanners. Determine if the port is reachable from non-trusted networks.Affected if Port 5010/tcp is accessible from network segments that are not explicitly trusted or whitelisted.
If the SPPA-T3000 MS3000 Migration Server is installed and port 5010/tcp is open and reachable from your network, the environment is affected by this vulnerability.
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 dataImplement strict network access controls to limit who can reach the MS3000 Migration Server on port 5010/tcp, ideally placing the system behind a DMZ or firewall with whitelisted IPs. If available, apply vendor patches; otherwise, monitor 5010/tcp for anomalous traffic patterns.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18330 — 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-18330 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