dbcve.org
Scalance X 200 FirmwareOperating system · Siemens

CVE-2019-6569

CRITICAL · 9.1 CVSS v3.1 Published 2019-03-26
Fix available
A fix is available. Upgrade to 4.1 / 4.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
The monitor barrier of the affected products insufficiently blocks data from being forwarded over the mirror port into the mirrored network. An attacker could use this behavior to transmit malicious packets to systems in the mirrored network, possibly influencing their configuration and runtime behavior.

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

A detailed technical summary for this CVE is being prepared.

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
Scalance X 200 FirmwareOperating system
Affected:< 5.2.4
Scalance X 300 FirmwareOperating system
Affected:< 4.1.3
Scalance Xp 200 FirmwareOperating system
Affected:< 4.1
Scalance Xc 200 FirmwareOperating system
Affected:< 4.1
Scalance Xf 200 FirmwareOperating system
Affected:< 4.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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.

dbcve · scoped
Upgrade available Upgrade to 4.1 / 4.1.3 / 5.2.4 or later
Fixed in 4.14.1.35.2.4
Vendor patch cert-portal.siemens.com →
Recommended fix High confidence

Scalance X 200: firmware 5.2.4; Scalance X 300: firmware 4.1.3; Scalance Xp/Xc/Xf 200: firmware 4.1

  1. Identify the exact Scalance X model (X 200, X 300, Xp 200, Xc 200, or Xf 200) currently deployed
  2. Check the current firmware version of the device through the web interface or CLI
  3. Access the Siemens security advisory at https://cert-portal.siemens.com/productcert/pdf/ssa-557804.pdf to obtain the correct firmware update
  4. Download the appropriate firmware version for your specific model from Siemens support (5.2.4 for X 200, 4.1.3 for X 300, or 4.1 for Xp/Xc/Xf 200)
  5. Upload and install the firmware update following Siemens standard firmware upgrade procedures (typically via web interface under 'Load & Save' or CLI)
  6. After reboot, verify the firmware version matches the expected fixed version
  7. Confirm the monitor port/mirror port now correctly blocks outbound data transmission to the mirrored network
Caveat Review Siemens release notes for any configuration or compatibility changes before upgrading; schedule maintenance window as firmware update may cause brief network disruption

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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