Skip to main content

Syself security assessment

GHSA-gcjh-h69q-9w9g in Syself Kubernetes

cel-go: JSON Private Fields Exposed via NativeTypes and ParseStructTag

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-gcjh-h69q-9w9g affects the ccm, cilium, cilium_operator, csi-hcloud, 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.

Not affected in 1.36 v10 Upstream severity: Medium Last assessed

Syself Kubernetes is not affected by GHSA-gcjh-h69q-9w9g in any of the 10 releases that ship ccm, cilium, cilium_operator, csi-hcloud, kube_apiserver, kube_controller_manager, kube_scheduler, metrics-server.

Reason: The vulnerable code is never executed.

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

ccm v2.0.7
Not affected Medium
The vulnerable code is never executed

The information leak needs program data structures to be made available to the expression engine. These components evaluate expressions only over plain data and never expose such structures, so it cannot happen.

Syself Security
kube_apiserver 1.36.6
Not affected Medium
The vulnerable code is never executed

This flaw can leak information only when internal program data types are exposed to the expression engine. These components run expressions over plain data and never expose those types.

Syself Security
kube_controller_manager 1.36.6
Not affected Medium
The vulnerable code is never executed

This flaw can leak information only when internal program data types are exposed to the expression engine. These components run expressions over plain data and never expose those types.

Syself Security
kube_scheduler 1.36.6
Not affected Medium
The vulnerable code is never executed

This flaw can leak information only when internal program data types are exposed to the expression engine. These components run expressions over plain data and never expose those types.

Syself Security
metrics-server 1.8.24
Not affected Medium
The vulnerable code is never executed

The flaw only affects programs that expose internal data objects to the CEL expression engine. These components run expressions over plain data and never do that, so the flawed code is not reached.

Syself Security

Status by release

ReleasesComponentStatusReasonFixed inAssessment
ccm v2.0.7Not affectedThe vulnerable code is never executed—Details
kube_apiserver 1.36.3, 1.36.4, 1.36.5, 1.36.6Not affectedThe vulnerable code is never executed—Details
kube_controller_manager 1.36.3, 1.36.4, 1.36.5, 1.36.6Not affectedThe vulnerable code is never executed—Details
kube_scheduler 1.36.3, 1.36.4, 1.36.5, 1.36.6Not affectedThe vulnerable code is never executed—Details
metrics-server 1.8.23, 1.8.24Not affectedThe vulnerable code is never executed—Details
cilium 1.20.0, 1.20.1, 1.20.2Not affectedThe vulnerable code is never executed—Details
cilium_operator 1.20.0, 1.20.1, 1.20.2Not affectedThe vulnerable code is never executed—Details
csi-hcloud v2.21.0, v2.22.1, v2.23.0Not affectedThe vulnerable code is never executed—Details

Frequently asked questions

My scanner reports GHSA-gcjh-h69q-9w9g in a Syself cluster. What should I do?

Scanners such as Trivy and Grype match package versions, so they report GHSA-gcjh-h69q-9w9g 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.