Security readout for executives and security teams
Plain-English summary
nvOC through 3.2 reused SSH host keys in its installation image. That means many systems could present the same server identity, weakening trust in SSH connections and making internet-exposed rigs easier to find. This is most relevant to cryptocurrency mining environments using nvOC.
Executive priority
Prioritize remediation where nvOC systems are internet-facing or used in environments with valuable wallets, credentials, or management access. The business concern is loss of trusted remote administration and easier discovery of mining infrastructure.
Technical view
This is CWE-321: hard-coded cryptographic keys. Reused SSH host keys let an attacker impersonate affected hosts in man-in-the-middle scenarios and allow fingerprint-based discovery of exposed public IPv4 nodes. The bundle identifies nvOC through 3.2 and does not confirm a released fixed image.
Likely exposure
Exposure is likely limited to nvOC mining rigs through version 3.2, especially systems reachable over public IPv4 with SSH enabled. Organizations without nvOC-based mining systems are unlikely to be affected based on the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The risk is still serious because the issue is remotely relevant, low complexity, and involves SSH identity reuse that can support impersonation and large-scale discovery.
Researcher notes
Evidence is strongest for the hard-coded SSH host key condition and discovery/MITM impact. Product metadata in the bundle is sparse, and the only fix statement says the vendor planned a future image build as of 2019-12-01.
Mitigation direction
- Inventory any nvOC systems and confirm whether they are version 3.2 or earlier.
- Regenerate unique SSH host keys on every affected nvOC installation.
- Restrict SSH exposure to trusted networks or VPN access only.
- Check vendor release history for an image build that removes baked-in host keys.
- Treat previously trusted SSH fingerprints from affected hosts as unreliable.
Validation and detection
- Compare SSH host key fingerprints across owned nvOC hosts for unintended reuse.
- Verify regenerated host keys remain unique after reboot and configuration management runs.
- Review firewall and cloud rules for public SSH exposure on mining rigs.
- Confirm asset inventory contains no unmanaged nvOC installations.
- Document whether a vendor-fixed image is available before reimaging.
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-19752 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
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.