Skip to content
Noroxi
NVD / CVE Program· CNA icscert

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

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.88% (FIRST EPSS); higher than 59.1% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.8 · v3.1—No exploit No fix recorded
Published
May 19, 2022
Updated
Jun 16, 2026
EPSS
0.8% · 59th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · icscert
7.2
1.6 point gap

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-16231

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for bachmann records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
bachmannmx207 firmware
bachmannmx207
bachmannmx213 firmware
bachmannmx213
bachmannmx220 firmware
bachmannmx220
bachmannmc206 firmware
bachmannmc206
bachmannmc212 firmware
bachmannmc212
bachmannmc220 firmware
bachmannmc220

and 28 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • bachmann cpc210 firmware1.06.14 and later
  • bachmann cs200 firmware1.06.14 and later
  • bachmann mc205 firmware1.06.14 and later
  • bachmann mc206 firmware1.06.14 and later
  • bachmann mc210 firmware1.06.14 and later
  • bachmann mc212 firmware1.06.14 and later
  • bachmann mc220 firmware1.06.14 and later
  • bachmann me203 firmware1.06.14 and later
  • bachmann mh212 firmware1.06.14 and later
  • bachmann mh230 firmware1.06.14 and later
  • bachmann mp213 firmware1.06.14 and later
  • bachmann mp226 firmware1.06.14 and later
  • bachmann mpc240 firmware1.06.14 and later
  • bachmann mpc265 firmware1.06.14 and later
  • bachmann mpc270 firmware1.06.14 and later
  • bachmann mpc293 firmware1.06.14 and later
  • bachmann mpe270 firmware1.06.14 and later
  • bachmann mx207 firmware1.06.14 and later
  • bachmann mx213 firmware1.06.14 and later
  • bachmann mx220 firmware1.06.14 and later

Versions reported by the vendor

Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.

  • Bachmann Electronic, GmbH M1 Hardware Controller CPC210

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller CS200

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller MC205

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller MC206

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller MC210

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller MC212

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller MC220

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller ME203

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller MH212

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller MH230

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller MP213

    • MSYS v1.06.14 and later · before All*affected

  • Bachmann Electronic, GmbH M1 Hardware Controller MP226

    • MSYS v1.06.14 and later · before All*affected

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-916 · Use of Password Hash With Insufficient Computational Effort

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records