Syself security assessment
OpenTelemetry Go SDK Vulnerable to Arbitrary Code Execution via PATH Hijacking
Syself Autopilot is fully managed Kubernetes on your own Hetzner servers. Every cluster runs a versioned cluster stack release, and this page tracks how GHSA-9h8m-3fm2-qjrq affects the ccm, csi-hcloud, etcd_image components those releases ship, based on Syself's assessments. For the general description and scoring of the vulnerability, see the references.
Syself Kubernetes is not affected by GHSA-9h8m-3fm2-qjrq in any of the 10 releases that ship ccm, csi-hcloud, etcd_image.
Reason: The vulnerable code is never executed.
The affected code only runs on Apple and BSD systems. These programs are built for Linux, so it is not included and never runs.
Syself SecurityThe affected part of the monitoring library only builds on non-Linux systems. These Linux images do not include it, so it never runs.
Syself SecurityScanners such as Trivy and Grype match package versions, so they report GHSA-9h8m-3fm2-qjrq whenever the vulnerable version is present, even when it cannot be exploited. Syself publishes its assessments as a VEX (Vulnerability Exploitability eXchange) document for every release. Pass it to your scanner to drop the findings Syself has assessed as not affected or fixed:
trivy image --vex hetzner-apalla-1-36-v10-advisory.openvex.json <image>
grype <image> --vex hetzner-apalla-1-36-v10-advisory.openvex.json Each assessment applies to the package version it names. A finding stays in the report when the document has no assessment for that package, or when the vulnerability is still affected or under investigation.
Download the OpenVEX document for 1.36 v10The severity shown is the upstream rating of the vulnerability itself. The status is Syself's assessment of whether it can be exploited in the components Syself ships, so a critical vulnerability can still be not affected.
Think this assessment is wrong, or found a vulnerability in Syself? Contact us.