CVE-2020-7542
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 · uneditedA CWE-754: Improper Check for Unusual or Exceptional Conditions vulnerability exists in Modicon M580, Modicon M340, Legacy Controllers Modicon Quantum & Modicon Premium (see security notifications for affected versions), that could cause denial of service when a specially crafted Read Physical Memory request over Modbus is sent to the controller.
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 confidenceA CWE-754 improper check for unusual or exceptional conditions vulnerability exists in Schneider Electric Modicon controllers (M580, M340, Quantum, Premium). When a specially crafted Read Physical Memory request over Modbus is sent to the controller, it fails to properly validate the request, leading to a denial of service condition where the controller becomes unresponsive or crashes.
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< 3.20< 3.20< 3.20< 3.20< 3.20< 3.20< 3.20< 3.20CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Modicon controller modelLocate the controller hardware nameplate or check the device configuration in Unity Pro/Unity XL programming software. Look for model numbers such as Bmep581020, Bmep582020, Bmep582040, Bmep583040, Bmep584020, Bmep584040, Bmep585040, Bmep586040, or other Modicon M580, M340, Quantum, or Premium modules.Affected if The controller model is a Modicon M580, M340, Quantum, or Premium series device.
-
Check firmware versionAccess the controller via Unity Pro/Unity XL programming software, EcoStruxure Control Expert, or the web server interface if available. Navigate to the firmware revision information. Compare the installed firmware version to the affected threshold of < 3.20 for M580 models.Affected if The installed firmware version is lower than 3.20 for M580 controllers, or unknown/earlier stable revisions for M340, Quantum, or Premium controllers.
-
Verify Modbus communication is enabledCheck the controller configuration in the programming software for Modbus TCP or Modbus Serial communication settings. Confirm whether Modbus protocol stacks (MBTCP, MBSLAVE) are loaded and active in the controller application.Affected if Modbus communication is enabled and the controller is configured to accept Modbus requests.
-
Assess network accessibility of Modbus portsReview network segmentation and firewall rules. Determine if the controller Modbus TCP port (typically 502) or Modbus Serial gateway is accessible from network segments other than a trusted engineering workstation VLAN. Use network scanning or review firewall policies.Affected if The Modbus service port (502/TCP) is open to untrusted network segments or the device is directly reachable from outside the control system DMZ.
You are affected if you have a Modicon M580, M340, Quantum, or Premium controller with firmware below 3.20 (for M580) that has Modbus communication enabled and is accessible over the network.
Generated from the published advisory. Verify against your own configuration.
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 data3.20
Apply available firmware updates from Schneider Electric's security notifications. If updates are unavailable, implement network segmentation to restrict Modbus access to trusted devices only and monitor for anomalous Read Physical Memory requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7542 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-7542 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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