Security readout for executives and security teams
Plain-English summary
minerstat msOS builds before October 23, 2019 reused an SSH key instead of giving each installation its own unique key. That weakens the trust boundary around remote administration of mining systems and can make affected rigs easier to impersonate or attack over exposed SSH services.
Executive priority
Prioritize remediation for any internet-accessible or remotely managed mining rigs. The issue is old but critical, and reused SSH identity material can undermine confidence in remote administration and incident containment.
Technical view
CVE-2019-19750 is a CWE-321 hard-coded key issue in minerstat msOS before 2019-10-23. The public record states instances lacked unique SSH keys. The assigned CVSS 3.1 score is 9.8, network exploitable with no privileges or user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where minerstat msOS images from before 2019-10-23 remain deployed, especially mining rigs with SSH reachable from untrusted networks. The CVE affected-product metadata is incomplete, so asset confirmation must rely on msOS build dates and vendor guidance.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. Public discussion links the issue to widespread SSH host key reuse in Ethereum mining rig operating systems. Treat internet-reachable SSH on old msOS builds as high risk.
Researcher notes
The public record is sparse: it identifies non-unique SSH keys, CWE-321, a critical CVSS vector, and references a minerstat commit plus independent research. It does not provide complete CPE data, detailed exploit evidence, or a named product version beyond before 2019-10-23.
Mitigation direction
- Identify and upgrade minerstat msOS builds older than 2019-10-23.
- Check minerstat guidance and the referenced commit for the vendor-supported fix.
- Ensure each deployed instance has unique SSH keys after remediation.
- Restrict SSH exposure to trusted management networks or VPN access.
- Rotate administrative credentials if old systems were remotely reachable.
Validation and detection
- Inventory msOS installations and record their build or image date.
- Confirm no production system runs an image older than 2019-10-23.
- Check whether SSH keys differ between deployed msOS instances.
- Review perimeter scans for SSH exposure on mining rig networks.
- Document remediation evidence for each affected rig or image.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-321: 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 lookupCVE-2019-19750 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Cryptographic Key
Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.