Tekton Pipelines: VolumeMount path restriction bypass via missing filepath.Clean in /tekton/ check
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, a validation bypass in the VolumeMount path restriction allows mounting volumes under restricted /tekton/ internal paths by using .. path traversal components. The restriction check uses strings.HasPrefix without filepath.Clean, so a path like /tekton/home/../results passes validation but resolves to /tekton/results at runtime. 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
Tekton Pipelines validates VolumeMount paths without resolving `..` components. Someone able to specify a VolumeMount path can use path traversal to mount a volume under a restricted `/tekton/` internal path.
Teams running Tekton Pipelines or using Go package github.com/tektoncd/pipeline should check versions from 1.0.0 before the applicable fixed release.