CVE-2020-10628
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 · uneditedControlEdge PLC (R130.2, R140, R150, and R151) and RTU (R101, R110, R140, R150, and R151) exposes unencrypted passwords on the network.
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 confidenceThe ControlEdge PLC and RTU devices expose unencrypted passwords on the network, allowing an unauthenticated attacker with network access to intercept or sniff these credentials. This is a high-severity confidentiality issue affecting specific firmware revisions (R130.2, R140, R150, R151 for PLCs and R101, R110, R140, R150, R151 for RTUs).
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= r130.2= r140= r150= r151= r101= r110= r140= r150= r151CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 device model and firmware versionAccess the ControlEdge PLC or RTU device web interface, console, or management interface and locate the firmware version information. This is typically found under System Info, Device Status, or Firmware/About sections.Affected if The firmware version matches R130.2, R140, R150, or R151 for PLCs, or R101, R110, R140, R150, or R151 for RTUs.
-
Capture network traffic on the PLC/RTU segmentUse a network packet capture tool (such as Wireshark or tcpdump) on the network segment where the ControlEdge device communicates. Monitor traffic for plaintext credential transmission, especially during authentication or device communication events.Affected if Network captures show usernames and passwords transmitted in cleartext without encryption protocols such as TLS or SSH.
-
Inspect communication protocols in useReview the device configuration and active services to determine which protocols are enabled for remote access and data transmission. Check for use of unencrypted protocols like HTTP, Telnet, or legacy industrial protocols without encryption wrappers.Affected if The device uses unencrypted protocols (HTTP, Telnet, unencrypted Modbus, etc.) for operator authentication or device management.
-
Verify encryption status of management interfacesAttempt to access the device web interface and note whether the connection uses HTTPS with valid certificates or HTTP. Also check if VPN or encrypted tunnels are required for remote access.Affected if Management interfaces are accessible over unencrypted HTTP without requiring VPN or TLS encryption.
A user is affected if their ControlEdge PLC or RTU runs one of the listed firmware versions AND network captures or interface inspection reveals that authentication credentials are transmitted in plaintext without encryption.
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 dataImplement network segmentation and encrypted communications (VPNs) to protect PLC/RTU traffic. Check vendor for firmware updates addressing credential encryption, and change exposed passwords immediately after assessment.
- Consultation8.0 h
- Implementation12.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 $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10628 — 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-10628 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