Tekton Pipelines git resolver has path traversal that allows reading arbitrary files from the resolver pod
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Starting in version 1.0.0 and prior to versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, and 1.10.2, the Tekton Pipelines git resolver is vulnerable to path traversal via the `pathInRepo` parameter. A tenant with permission to create `ResolutionRequests` (e.g. by creating `TaskRuns` or `PipelineRuns` that use the git resolver) can read arbitrary files from the resolver pod's filesystem, including ServiceAccount tokens. The file contents are returned base64-encoded in `resolutionrequest.status.data`. Versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, and 1.10.2 contain a patch.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- tektoncd pipeline
From 1.0.0 · fixed in 1.0.1; From 1.1.0 · fixed in 1.3.3; From 1.4.0 · fixed in 1.6.1; From 1.7.0 · fixed in 1.9.2; From 1.10.0 · fixed in 1.10.2
- github.com/tektoncd/pipelineGo
From 1.0.0 · fixed in 1.0.1
- github.com/tektoncd/pipelineGo
From 1.1.0 · fixed in 1.3.3
- github.com/tektoncd/pipelineGo
From 1.4.0 · fixed in 1.6.1
- github.com/tektoncd/pipelineGo
From 1.7.0 · fixed in 1.9.2
- github.com/tektoncd/pipelineGo
From 1.10.0 · fixed in 1.10.2
- github.com/tektoncd/pipelineGo
From 1.0.0 · fixed in 1.0.1; From 1.1.0 · fixed in 1.3.3; From 1.4.0 · fixed in 1.6.1; From 1.7.0 · fixed in 1.9.2; From 1.10.0 · fixed in 1.11.1