Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun
tektoncd pipeline
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/tektoncd/pipeline Go |
|
|
tektoncd pipeline
| Product | Affected | Fixed in |
|---|---|---|
| github.com/tektoncd/pipeline Go |
|
|
1.9.21.10.2Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Versions 0.60.0 through 1.0.0, 1.1.0 through 1.3.2, 1.4.0 through 1.6.0, 1.7.0 through 1.9.0, 1.10.0, and 1.10.1 have a denial-of-service vulnerability in that allows any user who can create a TaskRun or PipelineRun to crash the controller cluster-wide by setting .spec.taskRef.resolver (or .spec.pipelineRef.resolver) to a string of 31+ characters. The crash occurs because GenerateDeterministicNameFromSpec produces a name exceeding the 63-character DNS-1123 label limit, and its truncation logic panics on a [-1] slice bound since the generated name contains no spaces. Once crashed, the controller enters a CrashLoopBackOff on restart (as it re-reconciles the offending resource), blocking all CI/CD reconciliation until the resource is manually deleted. Built-in resolvers (git, cluster, bundles, hub) are unaffected due to their short names, but any custom resolver name triggers the bug. The fix truncates the resolver-name prefix instead of the full string, preserving the hash suffix for determinism and uniqueness. This issue has been patched in versions 1.0.1, 1.3.3, 1.6.1, 1.9.2 and 1.10.2.
From the CVE record · GitHub_M
Affected Tekton Pipelines versions can crash the controller when a user who can create a TaskRun or PipelineRun sets its resolver name to 31 or more characters. The controller can then enter CrashLoopBackOff while re-reconciling the resource, blocking CI/CD reconciliation until the resource is manually deleted.
Teams running github.com/tektoncd/pipeline versions >=0.60.0 <1.0.1, >=1.1.0 <1.3.3, >=1.4.0 <1.6.1, >=1.7.0 <1.9.2, or >=1.10.0 <1.10.2 should check their deployments.