{"id":"GHSA-p7pm-55hm-m74j","aliases":[],"summary":"Helm chart: Kubernetes export with rbac.scope ClusterRole grants cluster-wide Secret create","published_at":"2026-10-13T11:10:36Z","modified_at":"2026-10-13T11:10:36Z","products":[{"slug":"puppet","name":"Puppet / OpenVox","category":"iac"}],"rating":{"severity":"high","score":8,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H","attack_path":"internet_authenticated","user_interaction":false,"malicious":false},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"priority":9,"record_count":1,"vendors":["GitHub"],"details":"Before commit `0044f8a751a8`, when Kubernetes export was enabled, the chart always granted `create` on Secrets and ConfigMaps. With `rbac.scope: ClusterRole` that grant was cluster-wide, and the chart rendered it without refusing. A compromise of the CA pod could then escalate to any ServiceAccount in the cluster.\r\n\r\nFound in an independent audit at `fb856f1` and re-checked against `main` at `145cb53`.\r\n\r\n## Where\r\n\r\nLine numbers are as of `145cb53`, before the fix.\r\n\r\n- `charts/openvox-ca/templates/_helpers.tpl:799-801` granted `create` on `secrets` and `configmaps`. As the template comment says, `create` cannot be narrowed with `resourceNames`.\r\n- `_helpers.tpl:808-814` added unrestricted `patch` on both when the export targets could not be read from values (`existingConfigMap`, `args`, `--config`).\r\n- `templates/rbac.yaml:21-51` rendered the rules as a ClusterRole and ClusterRoleBinding when `rbac.scope: ClusterRole`. The CI fixture `ci/existing-config-values.yaml:31` used that scope.\r\n- The only response was a NOTES warning (`_helpers.tpl:891-905`), and it covered the `patch` grant only. `helm template`, Argo CD and Flux don't show NOTES. The chart did hard-`fail` the adjacent default-ServiceAccount case (`_helpers.tpl:633`).\r\n\r\nThe audit tied this to unknown targets. The `create` half applied to every ClusterRole install, with or without known targets.\r\n\r\n## Impact\r\n\r\n`create` on Secrets lets a principal create a `kubernetes.io/service-account-token` Secret annotated for any ServiceAccount in scope, which the token controller then fills in. Under a ClusterRole that includes `kube-system`. A code-execution or SSRF-to-API bug in the CA pod became cluster-admin-equivalent. Unrestricted `patch` also allowed overwriting arbitrary Secrets and ConfigMaps.\r\n\r\nNeither `docs/kubernetes-export.md` nor `docs/helm-chart.md` mentioned this. `values.yaml:310` said only \"Prefer Role\".\r\n\r\n## Fix\r\n\r\nFixed on `main` on 2026-10-13 in commit [`0044f8a751a80881bf5a0b978c57313aeaf2c7e8`](https://github.com/voxpupuli/openvox-ca/commit/0044f8a751a80881bf5a0b978c57313aeaf2c7e8) (PR #478, closes #473), Go module version `v0.0.0-20261013110456-0044f8a751a8`. The chart is released with the binaries, so the same commit fixes it.\r\n\r\n- `openvox-ca.validate` now fails the install when the chart would render the export RBAC as a ClusterRole, unless `kubernetesExport.rbac.allowClusterWideSecretCreate: true` is set. The message names the token-Secret escalation and points at `rbac.scope: Role` with each target namespace listed under `kubernetesExport.rbac.namespaces`. Only a real boolean `true` allows it, so a quoted `\"false\"` cannot slip through where schema validation is skipped.\r\n- When the cluster-wide grant is allowed, NOTES now warns about it as well as about the unnarrowed `patch` grant. The refusals, the warnings and `rbac.yaml` all read one helper, so they agree on when the export RBAC renders.\r\n- `docs/kubernetes-export.md` and `docs/helm-chart.md` now explain what `create` on Secrets allows, why `create` cannot be narrowed, and why nothing needs `ClusterRole`: a target either names its namespace or defaults to the release namespace, which the Role covers.\r\n- The ClusterRole CI fixture now sets the opt-in explicitly, and `chart:test` has reject and render cases for the refusal, the opt-in and the warning.\r\n\r\nWith `rbac.create: false` the chart creates no export RBAC, so neither the scope nor the opt-in has any effect, and the Role or ClusterRole an operator binds themselves is theirs to scope.\r\n\r\n## What to do\r\n\r\nIf you install the chart with `kubernetesExport.enabled: true` and `kubernetesExport.rbac.scope: ClusterRole`, move to `rbac.scope: Role` and list each namespace you export into under `kubernetesExport.rbac.namespaces`. A chart built from `0044f8a751a8` (2026-10-13) or later refuses the ClusterRole scope until you either do that or set `allowClusterWideSecretCreate: true`.\r\n\r\nOn earlier chart versions, `rbac.scope: Role` with the namespaces listed already confines the grant; nothing else is needed.","affected_stack":[{"ecosystem":"Go","package":"github.com/voxpupuli/openvox-ca","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20261013110456-0044f8a751a8"}]}],"fixed":["0.0.0-20261013110456-0044f8a751a8"],"provider":"github-repo-advisories","source":"GHSA-p7pm-55hm-m74j","relation":"self"}],"affected_other":[],"product_status":[],"records":[{"provider":"github-repo-advisories","source_id":"GHSA-p7pm-55hm-m74j","relation":"self","url":"https://github.com/voxpupuli/openvox-ca/security/advisories/GHSA-p7pm-55hm-m74j","license":"GitHub Terms of Service","published_at":"2026-10-13T11:10:36Z","modified_at":"2026-10-13T11:10:36Z","summary":"Helm chart: Kubernetes export with rbac.scope ClusterRole grants cluster-wide Secret create","details":"Before commit `0044f8a751a8`, when Kubernetes export was enabled, the chart always granted `create` on Secrets and ConfigMaps. With `rbac.scope: ClusterRole` that grant was cluster-wide, and the chart rendered it without refusing. A compromise of the CA pod could then escalate to any ServiceAccount in the cluster.\r\n\r\nFound in an independent audit at `fb856f1` and re-checked against `main` at `145cb53`.\r\n\r\n## Where\r\n\r\nLine numbers are as of `145cb53`, before the fix.\r\n\r\n- `charts/openvox-ca/templates/_helpers.tpl:799-801` granted `create` on `secrets` and `configmaps`. As the template comment says, `create` cannot be narrowed with `resourceNames`.\r\n- `_helpers.tpl:808-814` added unrestricted `patch` on both when the export targets could not be read from values (`existingConfigMap`, `args`, `--config`).\r\n- `templates/rbac.yaml:21-51` rendered the rules as a ClusterRole and ClusterRoleBinding when `rbac.scope: ClusterRole`. The CI fixture `ci/existing-config-values.yaml:31` used that scope.\r\n- The only response was a NOTES warning (`_helpers.tpl:891-905`), and it covered the `patch` grant only. `helm template`, Argo CD and Flux don't show NOTES. The chart did hard-`fail` the adjacent default-ServiceAccount case (`_helpers.tpl:633`).\r\n\r\nThe audit tied this to unknown targets. The `create` half applied to every ClusterRole install, with or without known targets.\r\n\r\n## Impact\r\n\r\n`create` on Secrets lets a principal create a `kubernetes.io/service-account-token` Secret annotated for any ServiceAccount in scope, which the token controller then fills in. Under a ClusterRole that includes `kube-system`. A code-execution or SSRF-to-API bug in the CA pod became cluster-admin-equivalent. Unrestricted `patch` also allowed overwriting arbitrary Secrets and ConfigMaps.\r\n\r\nNeither `docs/kubernetes-export.md` nor `docs/helm-chart.md` mentioned this. `values.yaml:310` said only \"Prefer Role\".\r\n\r\n## Fix\r\n\r\nFixed on `main` on 2026-10-13 in commit [`0044f8a751a80881bf5a0b978c57313aeaf2c7e8`](https://github.com/voxpupuli/openvox-ca/commit/0044f8a751a80881bf5a0b978c57313aeaf2c7e8) (PR #478, closes #473), Go module version `v0.0.0-20261013110456-0044f8a751a8`. The chart is released with the binaries, so the same commit fixes it.\r\n\r\n- `openvox-ca.validate` now fails the install when the chart would render the export RBAC as a ClusterRole, unless `kubernetesExport.rbac.allowClusterWideSecretCreate: true` is set. The message names the token-Secret escalation and points at `rbac.scope: Role` with each target namespace listed under `kubernetesExport.rbac.namespaces`. Only a real boolean `true` allows it, so a quoted `\"false\"` cannot slip through where schema validation is skipped.\r\n- When the cluster-wide grant is allowed, NOTES now warns about it as well as about the unnarrowed `patch` grant. The refusals, the warnings and `rbac.yaml` all read one helper, so they agree on when the export RBAC renders.\r\n- `docs/kubernetes-export.md` and `docs/helm-chart.md` now explain what `create` on Secrets allows, why `create` cannot be narrowed, and why nothing needs `ClusterRole`: a target either names its namespace or defaults to the release namespace, which the Role covers.\r\n- The ClusterRole CI fixture now sets the opt-in explicitly, and `chart:test` has reject and render cases for the refusal, the opt-in and the warning.\r\n\r\nWith `rbac.create: false` the chart creates no export RBAC, so neither the scope nor the opt-in has any effect, and the Role or ClusterRole an operator binds themselves is theirs to scope.\r\n\r\n## What to do\r\n\r\nIf you install the chart with `kubernetesExport.enabled: true` and `kubernetesExport.rbac.scope: ClusterRole`, move to `rbac.scope: Role` and list each namespace you export into under `kubernetesExport.rbac.namespaces`. A chart built from `0044f8a751a8` (2026-10-13) or later refuses the ClusterRole scope until you either do that or set `allowClusterWideSecretCreate: true`.\r\n\r\nOn earlier chart versions, `rbac.scope: Role` with the namespaces listed already confines the grant; nothing else is needed.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H","source":"GHSA-p7pm-55hm-m74j"}],"affected":[{"ecosystem":"Go","package":"github.com/voxpupuli/openvox-ca","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20261013110456-0044f8a751a8"}]}],"fixed":["0.0.0-20261013110456-0044f8a751a8"],"provider":"github-repo-advisories","source":"GHSA-p7pm-55hm-m74j","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/voxpupuli/openvox-ca/security/advisories/GHSA-p7pm-55hm-m74j"}]}],"references":[{"type":"ADVISORY","url":"https://github.com/voxpupuli/openvox-ca/security/advisories/GHSA-p7pm-55hm-m74j"}],"sources":[{"provider":"github-repo-advisories","source_id":"GHSA-p7pm-55hm-m74j","url":"https://github.com/voxpupuli/openvox-ca/security/advisories/GHSA-p7pm-55hm-m74j","license":"GitHub Terms of Service","modified_at":"2026-10-13T11:10:36Z","relation":"self"}]}
