CVE-2020-16231: The affected Bachmann Electronic M-Base Controllers of version MSYS v1.06.14 and later use weak cryptography t

This month

HIGH 7.2MITIGATEMITIGATEMITIGATE

CVE-2020-16231 is a high-severity flaw (CVSS 7.2) affecting mx207 firmware, mx213 firmware, mx220 firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-916
Published	2022-05-19
Last modified	2026-06-17

Publisher (CNA): ICS-CERT · Vendor: bachmann

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-05-19 18:15 UTCPublished CVE record published
2026-06-17 02:57 UTCUpdated Record last modified

bachmann mx207 firmware MITIGATE

Affected: >= 1.06.14

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.06.14

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

bachmann mx213 firmware MITIGATE

Affected: >= 1.06.14

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.06.14

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

bachmann mx220 firmware MITIGATE

Affected: >= 1.06.14

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.06.14

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

bachmann mc206 firmware MITIGATE

Affected: >= 1.06.14

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.06.14

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

bachmann mc212 firmware MITIGATE

Affected: >= 1.06.14

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.06.14

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

bachmann mc220 firmware MITIGATE

Affected: >= 1.06.14

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.06.14

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-16231?

mx207 firmware: mitigate or apply the listed mitigation; mx213 firmware: mitigate or apply the listed mitigation; mx220 firmware: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-16231 being exploited?

CVE-2020-16231 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-16231 affect?

CVE-2020-16231 affects mx207 firmware, mx213 firmware, mx220 firmware. Severity is high (CVSS 7.2). 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

How urgent is CVE-2020-16231?

Priority 40/100. High severity

References

← Back to latest CVEs