CVE & CISA-KEV Catalog

CVE-2020-16231

HIGH
7.2
CVSS v3
NVD

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.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredHigh
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

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

Exploit Intelligence

0.85%probability of exploitation in 30 days
55thpercentile

Moderate risk: more likely to be exploited than 55% of all known CVEs.

References

Third-Party Advisory1

Related Vulnerabilities

Other CWE-916 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2021-38314Medium5.329%--
CVE-2018-10618Critical9.810%-Fix
CVE-2005-0408Critical9.84.7%--
CVE-2023-33243High8.14.4%--
CVE-2020-14516Critical10.04.1%--
CVE-2024-21754Low1.83.5%-Fix

Common questions

How do I fix CVE-2020-16231?

No published fix for CVE-2020-16231 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2020-16231 being actively exploited?

Not that we know of. CVE-2020-16231 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.85% is the estimated probability that it will be exploited in the next 30 days. That is higher than 55% of all scored CVEs.

How severe is CVE-2020-16231?

CVE-2020-16231 has a CVSS v3 base score of 7.2, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2020-16231
CVE-2020-16231 severity badge

Markdown

[![CVE-2020-16231](https://tridentstack.com/cve/badge/CVE-2020-16231.svg)](https://tridentstack.com/cve/CVE-2020-16231)

HTML

<a href="https://tridentstack.com/cve/CVE-2020-16231"><img src="https://tridentstack.com/cve/badge/CVE-2020-16231.svg" alt="CVE-2020-16231"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.