# CVE-2020-16231: All Bachmann M1 System Processor Modules - Use of Password Hash with Insufficient Computational Effort

> Weak password hashing in Bachmann M1 controllers allows attackers to recover credentials and gain unauthorized access to industrial control systems.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-hqr7-c67h-hjrc

## What is CVE-2020-16231?

CVE-2020-16231 is a high-severity vulnerability in Bachmann Electronic, GmbH M1 Hardware Controller CPC210, published on 19 May 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The affected Bachmann Electronic M-Base Controllers of version MSYS v1.06.14 and later use weak cryptography to protect device passwords. Affected controllers that are actively supported include MX207, MX213, MX220, MC206, MC212, MC220, and MH230 hardware controllers, and affected end-of-life controller include MC205, MC210, MH212, ME203, CS200, MP213, MP226, MPC240, MPC265, MPC270, MPC293, MPE270, and CPC210 hardware controllers. Security Level 0 is set at default from the manufacturer, which could allow an unauthenticated remote attacker to gain access to the password hashes. Security Level 4 is susceptible if an authenticated remote attacker or an unauthenticated person with physical access to the device reads and decrypts the password to conduct further attacks.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2020-16231?

It affects 20 products.


Products: Bachmann Cpc210 Firmware, Bachmann Cs200 Firmware, Bachmann Mc205 Firmware, Bachmann Mc206 Firmware, Bachmann Mc210 Firmware, Bachmann Mc212 Firmware, Bachmann Mc220 Firmware, Bachmann Me203 Firmware, Bachmann Mh212 Firmware, Bachmann Mh230 Firmware, Bachmann Mp213 Firmware, Bachmann Mp226 Firmware, Bachmann Mpc240 Firmware, Bachmann Mpc265 Firmware, Bachmann Mpc270 Firmware, Bachmann Mpc293 Firmware, Bachmann Mpe270 Firmware, Bachmann Mx207 Firmware, Bachmann Mx213 Firmware, Bachmann Mx220 Firmware.

## How do I fix CVE-2020-16231?

No fix has been published for CVE-2020-16231 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-16231 being exploited?

There is no known exploitation of CVE-2020-16231 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-16231 and fix it if it is affected.

What it is: CVE-2020-16231 is a high-severity vulnerability in Bachmann Electronic, GmbH M1 Hardware Controller CPC210, published on 19 May 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-16231 in the wild and no public exploit code.

Affected product: Bachmann Electronic, GmbH M1 Hardware Controller CPC210. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-16231/ (Markdown: https://insights.sbomify.com/CVE-2020-16231/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-16231
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-16231
- OSV: https://osv.dev/vulnerability/CVE-2020-16231

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-16231/
Summaries are generated and may contain mistakes; the official description above is the record.