LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19751: easyMINE before 2019-12-05 ships with SSH host keys baked into the installation image, which allows man-in-...

easyMINE before 2019-12-05 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.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

easyMINE images before 2019-12-05 reused SSH host keys. That means different systems could look identical to SSH clients, weakening trust in remote administration and making Internet-wide discovery easier. The CVE is medium severity, not listed in KEV, and the supplied data does not prove active exploitation.

Executive priority

Treat this as a targeted operational hygiene issue, not an emergency based on the supplied evidence. Prioritize Internet-exposed mining infrastructure and any system where SSH trust matters for administration or monitoring.

Technical view

The flaw is improper SSH server host-key handling in easyMINE before 2019-12-05. Host keys were embedded in the installation image, enabling shared host identity across deployments. CVSS 3.1 is 5.6 with network attack vector, high complexity, no privileges, no user interaction, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on mining rigs or nodes installed from easyMINE images dated before 2019-12-05, especially where SSH is reachable from untrusted networks. The CVE record does not provide CPEs, vendor metadata, or a detailed product version matrix.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The described risk is man-in-the-middle potential and easy identification of public IPv4 nodes through reused SSH host keys. CVSS rates attack complexity as high.

Researcher notes

The CVE has sparse affected-product metadata and no CPEs in the supplied bundle. Analysis should focus on host-key uniqueness, image build date, public SSH exposure, and whether later easyMINE images changed host-key generation behavior.

Mitigation direction

  • Check easyMINE guidance for images released on or after 2019-12-05.
  • Replace affected installations with a corrected image when vendor guidance supports it.
  • Regenerate unique SSH host keys on systems built from older images.
  • Restrict SSH exposure to trusted networks or VPN access.
  • Monitor SSH host-key changes and unexpected remote administration activity.

Validation and detection

  • Inventory systems installed from easyMINE images before 2019-12-05.
  • Check whether multiple nodes share the same SSH host key fingerprint.
  • Confirm exposed SSH services are not reachable from the public Internet.
  • Review asset records for mining rigs using easyMINE-derived images.
  • Document vendor guidance found and remediation status for each affected host.
Prepared
Confidence
medium
Sources
4

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.

cwe · low confidence lookup

CWE-300: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-19751 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.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/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.6CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L2.23.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.6Medium
CVSS 3.1 vector shape for CVE-2019-19751Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-300 · source CWE mapping

Channel Accessible by Non-Endpoint

Channel Accessible by Non-Endpoint represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.