Tekton Pipelines: Git Resolver Unsanitized Revision Parameter Enables git Argument Injection Leading to RCE
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.3.41.0.2Tekton 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 git resolver's revision parameter is passed directly as a positional argument to git fetch without any validation that it does not begin with a - character. Because git parses flags from mixed positional arguments, an attacker can inject arbitrary git fetch flags such as --upload-pack=<binary>. Combined with the validateRepoURL function explicitly permitting URLs that begin with / (local filesystem paths), a tenant who can submit ResolutionRequest objects can chain these two behaviors to execute an arbitrary binary on the resolver pod. The tekton-pipelines-resolvers ServiceAccount holds cluster-wide get/list/watch on all Secrets, so code execution on the resolver pod enables full cluster-wide secret exfiltration. 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 git resolver passes an unvalidated revision to git fetch, allowing flag injection. A tenant who can submit ResolutionRequest objects can use a local filesystem URL to execute a binary on the resolver pod, potentially exposing cluster-wide Secrets. No additional user interaction is described.
Teams running github.com/tektoncd/pipeline versions 1.0.0 through 1.0.1, 1.1.0 through 1.3.3, 1.4.0 through 1.6.1, 1.7.0 through 1.9.2, or 1.10.0 through 1.11.0 should check their deployments.