Syself security assessment
gRPC-Go: xDS RBAC and HTTP/2 Vulnerabilities
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-hrxh-6v49-42gf affects the ccm, cilium_envoy, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, metrics-server, nvidia-device-plugin 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-hrxh-6v49-42gf in any of the 10 releases that ship ccm, cilium_envoy, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, metrics-server, nvidia-device-plugin.
Reason: The vulnerable code is never executed.
The affected permission engine is not used, and each bundled gRPC service listens only on a local file socket. No attacker-controlled network connection can reach the affected code.
Syself SecurityThe permission-check feature named in this flaw is not used. Every internal gRPC service listens only on a local socket file that outside traffic cannot reach, so an attacker cannot send the requests needed to trigger the flaw.
Syself SecurityThe affected gRPC access-control engine is not used here, and every gRPC service listens only on a local socket that outside traffic cannot reach. So no attacker can reach the affected code.
Syself SecurityThe affected permission engine is not used, and each bundled gRPC service listens only on a local file socket. No attacker-controlled network connection can reach the affected code.
Syself SecurityThe affected permission engine is not used, and each bundled gRPC service listens only on a local file socket. No attacker-controlled network connection can reach the affected code.
Syself SecurityThe affected permission engine is not used, and each bundled gRPC service listens only on a local file socket. No attacker-controlled network connection can reach the affected code.
Syself Security| Releases | Component | Status | Reason | Fixed in | Assessment |
|---|---|---|---|---|---|
| ccm v2.0.7 | Not affected | The vulnerable code is never executed | — | Details | |
| coredns 1.14.2 | Not affected | The vulnerable code is never executed | — | Details | |
| etcd_image 3.6.8-0 | Not affected | The vulnerable code is never executed | — | Details | |
| kube_apiserver 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | The vulnerable code is never executed | — | Details | |
| kube_controller_manager 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | The vulnerable code is never executed | — | Details | |
| kube_scheduler 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | The vulnerable code is never executed | — | Details | |
| metrics-server 1.8.23, 1.8.24 | Not affected | The vulnerable code is never executed | — | Details | |
| csi-hcloud v2.21.0, v2.22.1, v2.23.0 | Not affected | The vulnerable code is never executed | — | Details | |
| cilium_envoy v1.37.5-1782911245-7cffc778c923f68a77954a53b1a98d6b5353f004 | Not affected | The vulnerable code is never executed | — | Details | |
| nvidia-device-plugin v0.19.3 | Not affected | The vulnerable code is never executed | — | Details |
Scanners such as Trivy and Grype match package versions, so they report GHSA-hrxh-6v49-42gf 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.