Security readout for executives and security teams
Plain-English summary
Vanilla OS 2 Core image v1.1.0 reportedly shipped with static SSH service keys. Shared keys can let a suitably positioned attacker impersonate a host or intercept SSH trust decisions, creating confidentiality and availability risk during connections.
Executive priority
Prioritize affected Vanilla OS deployments that handle sensitive access paths or administrative SSH workflows. This is not currently evidenced as exploited, but static SSH keys weaken host identity and can undermine trusted remote administration.
Technical view
The CVE describes CWE-321 use of hard-coded cryptographic keys in the SSH service. CVSS 3.1 score is 6.4, with network attack vector, low complexity, high privileges required, and user interaction required. Published affected product metadata is incomplete.
Likely exposure
Exposure appears limited to systems built from Vanilla OS 2 Core image v1.1.0. The CVE record does not provide CPEs, package names, or complete affected-version ranges.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. The described attack is possible man-in-the-middle activity during SSH connections with other hosts.
Researcher notes
Key gaps are affected-version precision, fix status, and operational remediation details. Avoid expanding scope beyond Vanilla OS 2 Core image v1.1.0 unless vendor advisory or CVE updates confirm additional affected builds.
Mitigation direction
- Inventory systems built from Vanilla OS 2 Core image v1.1.0.
- Check the Vanilla OS advisory for fixed images or documented key-replacement guidance.
- Rebuild or replace affected images using vendor-approved updated media.
- Treat SSH trust involving affected hosts as suspect until keys are remediated.
Validation and detection
- Identify Vanilla OS 2 Core image version used for deployed systems.
- Review SSH host key provenance for systems built from the affected image.
- Confirm remediation against the GitHub advisory or vendor release notes.
- Monitor for unexpected SSH host key reuse across separate hosts.
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-2024-54855 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
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/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.
SSVC decision data
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:H/UI:R/S:U/C:H/I:L/A:H0.95.5CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Vanilla-OS/core-image/security/advisories/GHSA-67pc-hqr2-g34hCVE reference, mitre
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.