Security readout for executives and security teams
Plain-English summary
Bachmann M1 industrial controllers can protect device passwords with weak password-hash handling. On default Security Level 0, an unauthenticated remote attacker may access password hashes. That can support later compromise of controller access, especially where devices are reachable from untrusted networks.
Executive priority
Treat this as a high-priority OT credential exposure issue. It does not prove active compromise, but default configurations may expose password hashes remotely and affected systems can control industrial operations.
Technical view
CVE-2020-16231 is CWE-916 in Bachmann M-Base Controllers running MSYS v1.06.14 and later. Supported MX207, MX213, MX220, MC206, MC212, MC220, and MH230 controllers are listed, along with several end-of-life models. Security Level 4 still leaves exposure for authenticated remote attackers or physical access scenarios.
Likely exposure
Exposure is most likely in operational technology environments using listed Bachmann M1 controllers, especially devices left at default Security Level 0 or reachable over management networks. End-of-life models may carry higher operational risk because support options are limited.
Exploitation context
The bundle does not cite active exploitation, and the CVE is not marked KEV. The described risk is credential-material exposure: attackers may obtain password hashes remotely at Security Level 0, or under more constrained conditions at Security Level 4.
Researcher notes
Evidence is limited to the CVE bundle and CISA advisory reference. Do not assume a public exploit or vendor patch from this data alone. The key validation questions are model, MSYS version, Security Level, network reachability, authentication paths, and physical access.
Mitigation direction
- Inventory Bachmann M1 controllers and confirm MSYS versions against the affected list.
- Avoid Security Level 0 where operationally possible; document any exceptions.
- Restrict controller management access to trusted OT networks only.
- Protect physical access to controllers, cabinets, and maintenance ports.
- Consult Bachmann and CISA guidance for supported firmware or configuration fixes.
- Plan replacement or compensating controls for listed end-of-life controllers.
Validation and detection
- Confirm whether listed controller models are deployed in production or test OT environments.
- Record each controller model, MSYS version, support status, and configured Security Level.
- Verify management interfaces are not reachable from untrusted or corporate networks.
- Review access controls for authenticated users who can reach controllers remotely.
- Check physical security for sites where Security Level 4 exposure remains relevant.
- Look for unusual controller access or credential-related administrative activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-916: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-16231 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/uscert/ics/advisories/icsa-21-026-02CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Password Hash With Insufficient Computational Effort
Use of Password Hash With Insufficient Computational Effort represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.