dbcve.org
Telecontrol ConfiguratorApplication · Wago

CVE-2023-5188

HIGH · 7.5 CVSS v3.1 Published 2023-12-05
Fix available
A fix is available. Upgrade to 1.4.6.0 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
The MMS Interpreter of WagoAppRTU in versions below 1.4.6.0 which is used by the WAGO Telecontrol Configurator is vulnerable to malformed packets. An remote unauthenticated attacker could send specifically crafted packets that lead to a denial-of-service condition until restart of the affected device.

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 confidence

The MMS Interpreter of WagoAppRTU (used by WAGO Telecontrol Configurator) versions below 1.4.6.0 is vulnerable to malformed packet handling. A remote unauthenticated attacker can send specifically crafted packets causing a denial-of-service condition that persists until the affected device is restarted.

MitigationUpgrade WagoAppRTU to version 1.4.6.0 or later. In ICS environments, validate the update in a staging environment before production deployment and ensure network segmentation controls are in place to limit attack surface.

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
Telecontrol ConfiguratorApplication
Affected:all versions
WagoapprtuApplication
Affected:< 1.4.6.0

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. Locate WagoAppRTU installation
    Search for the WagoAppRTU application on the system. Check common installation directories for WAGO software such as C:\Program Files\WAGO or C:\Program Files (x86)\WAGO. Look for executables named WagoAppRTU.exe or related files.
    Affected if WagoAppRTU is found on the system and the version is below 1.4.6.0
  2. Determine installed version
    Right-click on the WagoAppRTU executable and select Properties, then navigate to the Details tab to view the File Version. Alternatively, check the software version displayed in the WAGO Telecontrol Configurator interface under Help or About.
    Affected if The installed version is anything below 1.4.6.0 or the version cannot be determined and WagoAppRTU is present
  3. Verify MMS Interpreter component is active
    Open Windows Task Manager or use the command line tasklist command to check if the WagoAppRTU process is running. The MMS Interpreter is the component within WagoAppRTU that processes MMS protocol packets.
    Affected if The WagoAppRTU process is running and handling MMS communications
  4. Check network exposure of the service
    Use netstat or a network scanning tool to identify which network ports WagoAppRTU is listening on. MMS typically uses TCP ports 102 or 502. Verify if these ports are exposed to untrusted networks.
    Affected if The service is listening on accessible network ports and reachable from network segments that contain untrusted or internet-facing systems
  5. Look for crash or restart indicators
    Review Windows Event Viewer Application logs for unexpected shutdowns, faulting modules, or restart events related to WagoAppRTU. Check for entries around the time of suspected attack activity.
    Affected if There are recent crash events or unexpected service restarts without clear cause

A system is affected if WagoAppRTU with a version below 1.4.6.0 is installed and the MMS Interpreter component is active, especially if the service is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 1.4.6.0 or later
Fixed in 1.4.6.0
Interim mitigation

Upgrade WagoAppRTU to version 1.4.6.0 or later. In ICS environments, validate the update in a staging environment before production deployment and ensure network segmentation controls are in place to limit attack surface.

Recommended fix High confidence

WagoAppRTU version 1.4.6.0

  1. 1. Navigate to the official WAGO website or the WAGO download portal.
  2. 2. Locate the WagoAppRTU software package.
  3. 3. Download version 1.4.6.0 or later of WagoAppRTU.
  4. 4. Back up the current configuration of the existing WagoAppRTU installation.
  5. 5. Uninstall or stop the current WagoAppRTU service.
  6. 6. Install the downloaded version 1.4.6.0.
  7. 7. Restore the configuration backup if needed.
  8. 8. Restart the WagoAppRTU service.

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

Fix this in Telecontrol Configurator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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