LiveActive security incident?Get immediate response
CVE Record

CVE-2020-5200: Minerbabe through V4.16 ships with SSH host keys baked into the installation image, which allows man-in-the...

Minerbabe through V4.16 ships with SSH host keys baked into the installation image, which allows man-in-the-middle attacks and makes identification of all public IPv4 nodes trivial with Shodan.io.

MediumCVSS 5.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Minerbabe mining systems through V4.16 used the same SSH host keys in installation images. That means many devices may look identical to SSH clients, weakening trust in remote administration and making internet-exposed nodes easy to fingerprint. The issue is not listed as actively exploited in KEV.

Executive priority

Treat this as a targeted infrastructure hygiene issue, not a critical internet-wide emergency. Prioritize public-facing Minerbabe systems and any environment where SSH administration protects wallet, mining, or infrastructure access.

Technical view

The CVE describes baked-in SSH host keys in Minerbabe through V4.16. Reused host keys undermine SSH server identity, enabling man-in-the-middle risk where traffic can be intercepted and allowing broad public IPv4 identification using Shodan-style fingerprinting. CVSS 3.1 score is 5.9, medium.

Likely exposure

Exposure is most likely in organizations or individuals running Minerbabe mining rig operating systems through V4.16, especially if SSH is reachable from public networks. The source bundle does not provide precise vendor, CPE, or deployment counts.

Exploitation context

No provided source or KEV entry confirms active exploitation. The practical risk is opportunistic identification of exposed Minerbabe nodes and possible SSH trust compromise if an attacker can position for traffic interception.

Researcher notes

Evidence is limited to the CVE record and referenced public write-up. The CVE names Minerbabe through V4.16 but structured affected-product metadata is incomplete. Avoid assuming patched versions unless confirmed in vendor materials.

Mitigation direction

  • Check Minerbabe vendor update guidance for versions after V4.16.
  • Upgrade or rebuild affected systems if vendor guidance provides a corrected image.
  • Ensure each deployed system has unique SSH host keys where supported.
  • Restrict SSH access to trusted networks, VPNs, or management hosts.
  • Investigate and rotate credentials if SSH interception is suspected.

Validation and detection

  • Inventory Minerbabe deployments and identify versions through V4.16.
  • Compare SSH host key fingerprints across systems for reuse.
  • Confirm whether SSH is exposed to public IPv4 addresses.
  • Review SSH client trust records for unexpected host identity changes.
  • Check vendor update notes for any host-key remediation guidance.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2020-5200 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L2.53.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2020-5200Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.