Syself security assessment
TEMP-0000000-F7A20F
Syself Autopilot is fully managed Kubernetes on your own Hetzner servers. Every cluster runs a versioned cluster stack release, and this page tracks how TEMP-0000000-F7A20F affects the kernel component 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 TEMP-0000000-F7A20F in any of the 10 releases that ship kernel.
Reason: An attacker cannot reach the vulnerable code.
This flaw lets a logged-in local user overload the system by making many isolated environments. Untrusted users cannot log in, and workloads are blocked from making them, so it cannot be triggered.
Syself Security| Releases | Component | Status | Reason | Fixed in | Assessment |
|---|---|---|---|---|---|
| kernel 6.18.42, 6.18.45, 6.18.49, 6.18.54, 6.18.59, 6.18.63 | Not affected | An attacker cannot reach the vulnerable code | — | Details |
Scanners such as Trivy and Grype match package versions, so they report TEMP-0000000-F7A20F 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.