Tekton Pipelines: Git resolver API mode leaks system-configured API token to user-controlled serverURL
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.6.21.9.31.11.1Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Starting in version 1.0.0 and prior to versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1, the Tekton Pipelines git resolver in API mode sends the system-configured Git API token to a user-controlled serverURL when the user omits the token parameter. A tenant with TaskRun or PipelineRun create permission can exfiltrate the shared API token (GitHub PAT, GitLab token, etc.) by pointing serverURL to an attacker-controlled endpoint. Versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 fix the issue.
From the CVE record · GitHub_M
The Tekton Pipelines git resolver in API mode sends the system-configured Git API token to a user-controlled serverURL when the token parameter is omitted. A tenant with TaskRun or PipelineRun create permission can point serverURL to an attacker-controlled endpoint and exfiltrate the shared token.
Teams running Tekton Pipelines or using Go package github.com/tektoncd/pipeline in versions >=1.0.0 <1.0.2, >=1.1.0 <1.3.4, >=1.4.0 <1.6.2, >=1.7.0 <1.9.3, or >=1.10.0 <1.11.1 should check their deployments.