Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| tektoncd | pipeline | affected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Tektoncd | Pipeline |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cv4x-93xx-wgfj | Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.383% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Linuxfoundation
Linuxfoundation tekton Pipelines |
|
| CPEs | cpe:2.3:a:linuxfoundation:tekton_pipelines:*:*:*:*:*:go:*:* | |
| Vendors & Products |
Linuxfoundation
Linuxfoundation tekton Pipelines |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-130 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tektoncd
Tektoncd pipeline |
|
| Vendors & Products |
Tektoncd
Tektoncd pipeline |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Tekton 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. | |
| Title | Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun | |
| Weaknesses | CWE-129 | |
| References |
| |
| Metrics |
cvssV3_1
|