Syself security assessment
OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs
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-8wmf-6v46-5gfg affects the ccm, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, metrics-server 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-8wmf-6v46-5gfg in any of the 10 releases that ship ccm, coredns, csi-hcloud, etcd_image, kube_apiserver, kube_controller_manager, kube_scheduler, metrics-server.
Reason: An attacker cannot reach the vulnerable code.
The information appears only when internal diagnostic logging is deliberately enabled, and it consists of operator-configured collector addresses. Revealing it requires access to the logs, not any untrusted network input.
Syself SecurityThis flaw can copy the configured telemetry endpoint address into verbose diagnostic logs, and only when such logging is deliberately enabled. It is chosen by the operator, never supplied by an attacker, so no outside party can trigger it.
Syself SecurityThe endpoint details are only written when internal diagnostic logging is explicitly enabled, and they consist of operator-provided collector settings recorded to local logs. No remote attacker can influence or read them.
Syself SecurityThe information appears only when internal diagnostic logging is deliberately enabled, and it consists of operator-configured collector addresses. Revealing it requires access to the logs, not any untrusted network input.
Syself SecurityThe information appears only when internal diagnostic logging is deliberately enabled, and it consists of operator-configured collector addresses. Revealing it requires access to the logs, not any untrusted network input.
Syself SecurityThis flaw can copy the configured telemetry endpoint address into verbose diagnostic logs, and only when such logging is deliberately enabled. It is chosen by the operator, never supplied by an attacker, so no outside party can trigger it.
Syself SecurityThe endpoint details are only written when internal diagnostic logging is explicitly enabled, and they consist of operator-provided collector settings recorded to local logs. No remote attacker can influence or read them.
Syself SecurityThe endpoint details are only written when internal diagnostic logging is explicitly enabled, and they consist of operator-provided collector settings recorded to local logs. No remote attacker can influence or read them.
Syself SecurityThis flaw can copy the configured telemetry endpoint address into verbose diagnostic logs, and only when such logging is deliberately enabled. It is chosen by the operator, never supplied by an attacker, so no outside party can trigger it.
Syself SecurityThe information appears only when internal diagnostic logging is deliberately enabled, and it consists of operator-configured collector addresses. Revealing it requires access to the logs, not any untrusted network input.
Syself SecurityThe endpoint details are only written when internal diagnostic logging is explicitly enabled, and they consist of operator-provided collector settings recorded to local logs. No remote attacker can influence or read them.
Syself SecurityThis flaw can copy the configured telemetry endpoint address into verbose diagnostic logs, and only when such logging is deliberately enabled. It is chosen by the operator, never supplied by an attacker, so no outside party can trigger it.
Syself SecurityThe information appears only when internal diagnostic logging is deliberately enabled, and it consists of operator-configured collector addresses. Revealing it requires access to the logs, not any untrusted network input.
Syself SecurityThe endpoint details are only written when internal diagnostic logging is explicitly enabled, and they consist of operator-provided collector settings recorded to local logs. No remote attacker can influence or read them.
Syself SecurityThis flaw can copy the configured telemetry endpoint address into verbose diagnostic logs, and only when such logging is deliberately enabled. It is chosen by the operator, never supplied by an attacker, so no outside party can trigger it.
Syself SecurityThe information appears only when internal diagnostic logging is deliberately enabled, and it consists of operator-configured collector addresses. Revealing it requires access to the logs, not any untrusted network input.
Syself SecurityThe information appears only when internal diagnostic logging is deliberately enabled, and it consists of operator-configured collector addresses. Revealing it requires access to the logs, not any untrusted network input.
Syself SecurityThe endpoint details are only written when internal diagnostic logging is explicitly enabled, and they consist of operator-provided collector settings recorded to local logs. No remote attacker can influence or read them.
Syself SecurityThis flaw can copy the configured telemetry endpoint address into verbose diagnostic logs, and only when such logging is deliberately enabled. It is chosen by the operator, never supplied by an attacker, so no outside party can trigger it.
Syself Security| Releases | Component | Status | Reason | Fixed in | Assessment |
|---|---|---|---|---|---|
| ccm v2.0.7 | Not affected | An attacker cannot reach the vulnerable code | — | Details | |
| coredns 1.14.2 | Not affected | An attacker cannot reach the vulnerable code | — | Details | |
| etcd_image 3.6.8-0 | Not affected | An attacker cannot reach the vulnerable code | — | Details | |
| kube_apiserver 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | An attacker cannot reach the vulnerable code | — | Details | |
| kube_controller_manager 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | An attacker cannot reach the vulnerable code | — | Details | |
| kube_scheduler 1.36.3, 1.36.4, 1.36.5, 1.36.6 | Not affected | An attacker cannot reach the vulnerable code | — | Details | |
| metrics-server 1.8.23, 1.8.24 | Not affected | An attacker cannot reach the vulnerable code | — | Details | |
| csi-hcloud v2.21.0, v2.22.1, v2.23.0 | Not affected | An attacker cannot reach the vulnerable code | — | Details |
Scanners such as Trivy and Grype match package versions, so they report GHSA-8wmf-6v46-5gfg 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.