dbcve.org
Modicon M580 FirmwareOperating system · Schneider Electric

CVE-2023-25619

HIGH · 7.5 CVSS v3.1 Published 2023-04-19
Fix available
A fix is available. Upgrade to 3.51 / 4.10 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
A CWE-754: Improper Check for Unusual or Exceptional Conditions vulnerability exists that could cause denial of service of the controller when communicating over the Modbus TCP protocol.

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 vulnerability is a CWE-754 (Improper Check for Unusual or Exceptional Conditions) in a controller's Modbus TCP protocol implementation. The software fails to properly handle unusual or exceptional conditions during Modbus TCP communication, leading to a denial of service state on the controller.

MitigationImplement proper validation and exception handling for all Modbus TCP input processing paths to ensure unusual or exceptional conditions are caught and handled safely without causing controller crash or DoS.

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
Modicon M580 FirmwareOperating system
Affected:< 4.10
Modicon M340 FirmwareOperating system
Affected:< 3.51
Modicon Momentum Unity M1e Processor FirmwareOperating system
Affected:all versions
Modicon Mc80 FirmwareOperating system
Affected:all versions
Tsxp57 FirmwareOperating system
Affected:all versions
Bmep58s FirmwareOperating system
Affected:all versions
Bmeh58s 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 the controller model
    Locate the Schneider Electric controller on the network or physically inspect the hardware labeling to determine the exact model (e.g., Modicon M580, Modicon M340, Modicon Momentum M1e, Modicon Mc80, Tsxp57, Bmep58s, or Bmeh58s)
    Affected if The controller is any of the models listed in the affected products (M580, M340, Momentum M1e, Mc80, Tsxp57, Bmep58s, or Bmeh58s)
  2. Determine the firmware version
    Access the controller's web interface, management software (e.g., Unity Pro, EcoStruxure), or console to retrieve the current firmware version. Consult vendor documentation for the specific command or menu path for your model.
    Affected if The firmware version is below the safe threshold: M580 < 4.10, M340 < 3.51, or for M1e, Mc80, Tsxp57, Bmep58s, Bmeh58s the version is any (all versions affected)
  3. Verify Modbus TCP is enabled
    Check the controller configuration through its programming software or web interface to confirm whether the Modbus TCP protocol stack is actively configured or running. Look for Modbus TCP communication settings, slave/server configuration, or Ethernet communication modules.
    Affected if Modbus TCP is enabled and actively used on the controller (the vulnerability only manifests when Modbus TCP communication is configured)
  4. Monitor for unexpected controller resets
    Review system logs, controller event logs, or operator interfaces for reports of unexplained controller crashes, restarts, or communication failures occurring during Modbus TCP traffic
    Affected if The controller experiences unexplained denial of service events or resets correlated with Modbus TCP activity

A user is affected if they have a vulnerable Schneider Electric controller (Modicon M580 with firmware < 4.10, M340 < 3.51, or any M1e/Mc80/Tsxp57/Bmep58s/Bmeh58s) with Modbus TCP protocol enabled and they observe unexplained controller resets or DoS conditions during Modbus TCP communication.

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 3.51 / 4.10 or later
Fixed in 3.514.10
Interim mitigation

Implement proper validation and exception handling for all Modbus TCP input processing paths to ensure unusual or exceptional conditions are caught and handled safely without causing controller crash or DoS.

Recommended fix Moderate confidence

Modicon M580: firmware >= 4.10; Modicon M340: firmware >= 3.51; Other affected products: contact vendor for fix availability

  1. 1. Identify the specific Modicon controller model and current firmware version in your environment
  2. 2. For Modicon M580: Navigate to Schneider Electric download portal (download.schneider-electric.com) and download firmware version 4.10 or later
  3. 3. For Modicon M340: Download firmware version 3.51 or later from the same portal
  4. 4. Follow Schneider Electric's official firmware update procedure for your controller - typically requires using Unity Pro or EcoStruxure Control Expert programming software
  5. 5. Verify the firmware update was successful by checking the controller's firmware version
  6. 6. Test Modbus TCP communication to confirm normal operation
  7. 7. For products listed as 'all versions' affected (Momentum M1e, Mc80, Tsxp57, Bmep58s, Bmeh58s), contact Schneider Electric technical support to inquire about available patches or mitigations
Caveat Firmware updates on industrial controllers may require coordination with operations; ensure backup of project and have rollback plan; some legacy features may be deprecated in newer firmware

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

Fix this in Modicon M580 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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