dbcve.org
750 363\/040 000 FirmwareOperating system · Wago

CVE-2023-1150

HIGH · 7.5 CVSS v3.1 Published 2023-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Uncontrolled resource consumption in Series WAGO 750-3x/-8x products may allow an unauthenticated remote attacker to DoS the MODBUS server with specially crafted packets.

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 WAGO 750-3x/-8x series controllers contain a MODBUS server implementation vulnerable to uncontrolled resource consumption. Specially crafted MODBUS packets can exhaust server resources, causing denial of service. The vulnerability is exploitable remotely without authentication, allowing attackers to crash the MODBUS service.

MitigationApply vendor firmware updates when available. In the interim, implement network segmentation to isolate OT assets and restrict MODBUS traffic to authorized endpoints using firewalls or access control lists.

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
750 363\/040 000 FirmwareOperating system
Affected:< fw11
750 362\/040 000 FirmwareOperating system
Affected:< fw11
750 362\/000 001 FirmwareOperating system
Affected:< fw11
750 891 FirmwareOperating system
Affected:< fw11
750 365\/040 010 FirmwareOperating system
Affected:< fw11
750 364\/040 010 FirmwareOperating system
Affected:< fw11
750 362 FirmwareOperating system
Affected:< fw11
750 363 FirmwareOperating system
Affected:< fw11

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 the WAGO controller model
    Locate the model number on the device label or check the device documentation/web interface. Look for model numbers: 750-363, 750-362, 750-364, 750-365, or 750-891.
    Affected if The model number matches one of these: 750-363, 750-362, 750-364, 750-365, or 750-891.
  2. Determine the installed firmware version
    Access the WAGO controller web interface or use the WAGO Configuration Studio to read the firmware version. The version is typically displayed in the device info or system status page.
    Affected if The firmware version is shown as a version number lower than fw11, or the version cannot be confirmed as fw11 or higher.
  3. Verify MODBUS server is enabled
    Check the controller configuration settings. In the WAGO web interface, navigate to Services or Communication settings to confirm if the MODBUS server (MODBUS TCP) is enabled and running.
    Affected if MODBUS TCP server is enabled and listening on the network.
  4. Check network exposure of MODBUS service
    Review network firewall rules and access control lists to determine if the MODBUS port (typically port 502) is accessible from untrusted networks or the internet.
    Affected if MODBUS port 502 is accessible from untrusted network segments or directly from the internet.

The device is affected if it is a WAGO 750-3x/750-8x series controller (models 750-362, 750-363, 750-364, 750-365, or 750-891) running firmware version below fw11, with MODBUS TCP server enabled and exposed on the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available. In the interim, implement network segmentation to isolate OT assets and restrict MODBUS traffic to authorized endpoints using firewalls or access control lists.

Recommended fix High confidence

Firmware fw11 or later for WAGO 750-3x/-8x series controllers (750-362, 750-363, 750-364, 750-365, 750-891)

  1. 1. Identify the specific WAGO 750 series controller model (e.g., 750-363, 750-362, 750-891, etc.) in your environment from the affected product list.
  2. 2. Access the WAGO controller's web interface or use WAGO's programming software (e.g., e!COCKPIT or CODESYS) to check the current firmware version.
  3. 3. If firmware version is below fw11, download the latest firmware version fw11 or later from the official WAGO website or support portal.
  4. 4. Follow WAGO's standard firmware update procedure: typically via the web interface under 'Firmware Update' or using the programming tool's firmware update function.
  5. 5. Verify the firmware update was successful by checking the firmware version after the update.
  6. 6. Test that the MODBUS server is functioning properly after the update.
  7. 7. Implement network segmentation and firewall rules to limit MODBUS traffic to trusted sources as an additional mitigation measure while updating.
Caveat Ensure compatibility with existing MODBUS configurations and verify that any custom applications function correctly with the new firmware version

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

Fix this in 750 363\/040 000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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