CVE-2019-18322
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 be able to read and write arbitrary files on the local file system by sending specifically crafted packets to port 5010/tcp. This vulnerability is independent from CVE-2019-18321. 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 confidenceArbitrary file read/write vulnerability in SPPA-T3000 MS3000 Migration Server. Attackers with network access to port 5010/tcp can send crafted packets to read and write arbitrary files on the local file system. The CVSS 9.1 indicates complete file system compromise is possible.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 installedCheck for the presence of the Migration Server component in the system inventory or installed programs. Look for Siemens SPPA-T3000 related processes or services running on the host.Affected if The SPPA-T3000 MS3000 Migration Server component is present on the system.
-
Verify port 5010/tcp is listeningRun command 'netstat -an | findstr 5010' or 'ss -tlnp | grep 5010' to check if port 5010 is in LISTEN state.Affected if Port 5010/tcp is open and listening on any interface.
-
Check network exposure of port 5010Use nmap or similar tool to determine if port 5010 is accessible from network segments outside the expected isolated zone: 'nmap -p 5010 <target_ip>' or review firewall rules for port 5010.Affected if Port 5010/tcp is accessible from untrusted network segments or the internet.
-
Confirm MS3000 Migration Server is exposedAttempt a controlled TCP connection to port 5010 from an untrusted network perspective: 'telnet <target> 5010' or 'nc -zv <target> 5010'.Affected if The connection succeeds, indicating the vulnerable service is network-accessible.
The environment is affected if the SPPA-T3000 MS3000 Migration Server is installed with port 5010/tcp accessible from any network segment that is not strictly isolated.
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 dataIsolate the MS3000 Migration Server on a restricted network segment and block external access to port 5010/tcp until vendor patch is available; implement strict network segmentation per ICS security best practices.
- Consultation12.0 h
- Implementation16.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18322 — 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-18322 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