Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-30234 is a high-severity Use of Hard-coded Cryptographic Key (CWE-321) vulnerability in Tritondatacenter (inferred from references). Its CVSS base score is 8.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Private Keys (T1552.004); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-30234 is a vulnerability in SmartOS, as used in Triton Data Center and other products, involving static host SSH keys embedded in the 60f76fd2-143f-4f57-819b-1ae32684e81b image—a Debian 12 LX zone image from 2024-07-26. Published on 2025-03-19, it is associated with CWE-321 (Use of Hard-coded Cryptographic Key) and carries a CVSS v3.1 base score of 8.3 (AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H).
An attacker on an adjacent network (AV:A) with no privileges (PR:N) and no user interaction (UI:N) can exploit this high-complexity (AC:H) issue. Exploitation enables high-impact confidentiality, integrity, and availability effects (C:I:A:H) across a changed scope (S:C), potentially allowing unauthorized access or control via the static SSH keys.
Advisories with mitigation guidance include Triton Data Center's TPS-2025-002 at https://security.tritondatacenter.com/tps-2025-002/, a SmartOS discussion thread at https://smartos.topicbox.com/groups/smartos-discuss/Ta6f13072e6bedddc-M3702e993edd7d6ce8d78dfc8, and an oss-security mailing list post at https://www.openwall.com/lists/oss-security/2025/03/13/10.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6719
Vulnerability Data
SmartOS, as used in Triton Data Center and other products, has static host SSH keys in the 60f76fd2-143f-4f57-819b-1ae32684e81b image (a Debian 12 LX zone image from 2024-07-26).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requiring cryptographic keys to be established and managed according to defined requirements prevents developers from embedding static unchangeable keys.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-SDLC activities such as code review and secret scanning directly prevent embedding static keys.
Data-at-rest protection policies require proper key management and therefore discourage hard-coded keys.
Data-in-transit protection similarly depends on non-hard-coded keys for encryption.
Configuration baselines and reviews can prohibit hard-coded keys in deployed artifacts.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Key-management controls that govern generation, rotation and protection of keys make the use of embedded hard-coded cryptographic keys less likely and easier to detect.