dbcve.org
Cp1604 FirmwareOperating system · Siemens

CVE-2019-10923

HIGH · 7.5 CVSS v3.1 Published 2019-10-10
Fix available
A fix is available. Upgrade to 2.8 / 4.1.1 or later.
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
An attacker with network access to an affected product may cause a denial of service condition by breaking the real-time synchronization (IRT) of the affected installation.

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

This is a denial of service vulnerability affecting real-time synchronization (IRT) in an affected product. An attacker with network access can exploit this to break the IRT synchronization, causing the affected installation to lose real-time synchronization capabilities.

MitigationRestrict network access to the affected product and implement network segmentation. If available, apply vendor-supplied patches that address the IRT synchronization vulnerability.

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
Cp1604 FirmwareOperating system
Affected:< 2.8
Cp1616 FirmwareOperating system
Affected:< 2.8
Dk Standard Ethernet Controller FirmwareOperating system
Affected:< 4.1.1= 4.1.1
Ek Ertec 200 FirmwareOperating system
Affected:< 4.5.0= 4.5.0
Ek Ertec 200p FirmwareOperating system
Affected:< 4.5.0
Scalance X 200irt FirmwareOperating system
Affected:< 5.2.1
Simatic Et 200m FirmwareOperating system
Affected:all versions
Simatic Et 200s FirmwareOperating system
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 affected product in inventory
    Locate any Siemens Cp1604, Cp1616, DK Standard Ethernet Controller, EK Ertec 200, EK Ertec 200p, Scalance X 200IRT, Simatic ET 200m, or Simatic ET 200s devices on your network or asset inventory
    Affected if None of the listed products are present in the environment
  2. Check firmware version on Cp1604 or Cp1616
    Access the device web interface, management console, or use SNMP to query the firmware version. Compare against the affected range < 2.8
    Affected if Firmware version is 2.7.x or lower, or the device firmware has not been upgraded to version 2.8 or later
  3. Check firmware version on DK Standard Ethernet Controller
    Access the device management interface or use Siemens management tools to retrieve the firmware version. Compare against affected range < 4.1.1 or = 4.1.1
    Affected if Firmware version is 4.1.1 or any version below 4.1.1 such as 4.1.0.x or earlier
  4. Check firmware version on EK Ertec 200 or EK Ertec 200p
    Access the device configuration interface or use Siemens management software to determine firmware version. Compare against affected ranges < 4.5.0 or = 4.5.0
    Affected if Firmware version is 4.5.0 or any version below 4.5.0 such as 4.4.x or earlier
  5. Check firmware version on Scalance X 200IRT
    Access the device web interface or use network management tools to query the firmware version. Compare against affected range < 5.2.1
    Affected if Firmware version is 5.2.0 or lower
  6. Verify IRT real-time synchronization is enabled
    Check the device configuration settings for IRT (Isochronous Real-Time) or real-time synchronization feature status. This is typically found in the device network or PROFINET configuration settings
    Affected if IRT or real-time synchronization functionality is actively configured or in use on the device

You are affected if you have any Cp1604, Cp1616, DK Standard Ethernet Controller, EK Ertec 200, EK Ertec 200p, Scalance X 200IRT, ET 200m, or ET 200s device with a firmware version matching the affected ranges (or any version for ET 200m/ET 200s) AND IRT real-time synchronization is enabled on that device.

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
Upgrade available Upgrade to 2.8 / 4.1.1 / 4.5.0 or later
Fixed in 2.84.1.14.5.0
Interim mitigation

Restrict network access to the affected product and implement network segmentation. If available, apply vendor-supplied patches that address the IRT synchronization vulnerability.

Fix this in Cp1604 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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