Security readout for executives and security teams
Plain-English summary
Some HiveOS mining-rig images reused the same SSH server identity keys. That can let an attacker impersonate a device during SSH connections, creating confidentiality risk if users accept the wrong host identity.
Executive priority
Treat this as a medium-priority exposure issue for mining infrastructure. It threatens confidentiality of administration sessions, not direct remote code execution based on the supplied evidence.
Technical view
CVE-2019-19754 is CWE-321: use of hard-coded cryptographic keys. HiveOS through 0.6-102@191212 reportedly shipped SSH host keys inside the installation image, enabling SSH man-in-the-middle risk and making public IPv4 nodes easier to identify.
Likely exposure
Exposure is limited to HiveOS deployments through 0.6-102@191212, especially mining rigs reachable over public IPv4 or managed over untrusted networks.
Exploitation context
The bundle does not show KEV listing or active exploitation. The described risk is practical identification of affected nodes and SSH man-in-the-middle exposure when users connect and accept reused host identities.
Researcher notes
Affected product metadata in the bundle is sparse, but the narrative names HiveOS through 0.6-102@191212. No patch version is identified in the provided sources, so validation should focus on image provenance, duplicated SSH host keys, and vendor guidance.
Mitigation direction
- Check HiveOS changelog and vendor guidance for corrected images or official remediation.
- Identify and prioritize internet-reachable HiveOS nodes for review.
- Restrict SSH access to trusted management networks while remediation is assessed.
- Where vendor guidance supports it, replace shared SSH host keys with unique per-host keys.
- Rebuild affected systems from fixed installation media when available.
Validation and detection
- Inventory HiveOS systems and confirm whether versions are through 0.6-102@191212.
- Review SSH host key fingerprints across nodes for unexpected duplication.
- Check whether affected rigs are reachable on public IPv4 addresses.
- Confirm administrators verify SSH host key changes before trusting connections.
- Document whether vendor guidance or fixed media has been applied.
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-19754 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
- Medium
- CVSS
- 5.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.13.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.7MediumVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Source materials
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.