CVE-2020-7567
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-311: Missing Encryption of Sensitive Data vulnerability exists in Modicon M221 (all references, all versions) that could allow the attacker to find the password hash when the attacker has captured the traffic between EcoStruxure Machine - Basic software and Modicon M221 controller and broke the encryption keys.
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 confidenceThe Modicon M221 PLC has a CWE-311 vulnerability where password hashes are not properly encrypted during transmission between EcoStruxure Machine - Basic software and the controller. An attacker who has already compromised encryption keys and captured network traffic can recover the plaintext password hashes.
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 dataall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 M221 PLC in your environmentLocate any Modicon M221 programmable logic controllers (PLCs) by reviewing asset inventories, network scans, or physical inspection of equipment labelsAffected if A Modicon M221 PLC is present in the environment
-
Confirm firmware version of the M221 PLCConnect to the PLC via EcoStruxure Machine - Basic or use the PLC web server (if enabled) to retrieve the firmware version from the controller properties or system informationAffected if The controller is running any firmware version (all versions are affected)
-
Verify EcoStruxure Machine - Basic software is in useCheck if EcoStruxure Machine - Basic engineering software is used to program or configure the M221 PLC by reviewing software installations or project filesAffected if EcoStruxure Machine - Basic is used to communicate with the M221 PLC
-
Inspect network traffic between engineering workstation and PLCCapture and analyze network packets on the segment between the EcoStruxure Machine - Basic workstation and the M221 PLC to verify if password data or authentication exchanges are transmitted with proper encryption (TLS or equivalent)Affected if Password hashes or authentication data is transmitted in cleartext or with weak encryption between the software and controller
-
Assess encryption key integrityReview security logs, key management procedures, and access controls to determine whether encryption keys used for PLC communications could have been compromisedAffected if Encryption keys have been compromised or key management lacks proper protection
Your environment is affected if you have a Modicon M221 PLC running any firmware version and use EcoStruxure Machine - Basic software, with password data transmitted without proper encryption or with compromised encryption keys.
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 dataUpdate to vendor-provided firmware that implements proper encryption for password data. Additionally, implement network segmentation and monitoring to prevent attackers from capturing traffic and compromising encryption keys in the first place.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2020-7567 — 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-7567 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