Skip to main content

Syself security assessment

GHSA-6v2p-p543-phr9 in Syself Kubernetes

golang.org/x/oauth2 Improper Validation of Syntactic Correctness of Input vulnerability

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-6v2p-p543-phr9 affects the cluster-proportional-autoscaler, metrics-server components those releases ship, based on Syself's assessments. For the general description and scoring of the vulnerability, see the references.

Not affected in 1.36 v10 Upstream severity: High Last assessed

Syself Kubernetes is not affected by GHSA-6v2p-p543-phr9 in any of the 10 releases that ship cluster-proportional-autoscaler, metrics-server.

Reason: An attacker cannot reach the vulnerable code.

Our assessment in 1.36 v10, the newest release with this finding

An attacker cannot reach the vulnerable code

The token-parsing memory issue needs an attacker-supplied token. These components read only tokens issued by trusted platform and Kubernetes sources, so the bad input cannot be introduced.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
cluster-proportional-autoscaler v1.10.3, v1.11.0Not affectedAn attacker cannot reach the vulnerable code—Details
metrics-server 1.8.23Not affectedAn attacker cannot reach the vulnerable code—Details

Frequently asked questions

My scanner reports GHSA-6v2p-p543-phr9 in a Syself cluster. What should I do?

Scanners such as Trivy and Grype match package versions, so they report GHSA-6v2p-p543-phr9 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 v10

What do the statuses mean?

Not affected
The component ships in the release, but Syself has assessed that the vulnerability cannot be exploited there. The reason column says why.
Fixed
The release ships a version of the component that carries the fix.
Affected
The vulnerability can affect the release. Upgrade to a release listed as fixed once one is available.
Under Investigation
Syself is still assessing whether the vulnerability affects the release.

Why can the severity differ from other sources?

The 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.

References

Think this assessment is wrong, or found a vulnerability in Syself? Contact us.