github.com/tektoncd/pipeline vulnerabilities
- Registry
- Go
- Latest
- 1.18.0
16 known advisories
The latest version, 1.18.0, is affected by 1 of them.
Is your project on an affected github.com/tektoncd/pipeline?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for github.com/tektoncd/pipeline
Tekton Pipelines VolumeMount path restriction bypass via missing filepath.Clean in github.com/tektoncd/pipeline
- Affected
- >=1.0.0 <1.0.2 · >=1.1.0 <1.3.4 · >=1.4.0 <1.6.2 · >=1.7.0 <1.9.3 · >=1.10.0 <1.11.1
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Tekton Pipelines git resolver leaks API token to user-controlled serverURL in github.com/tektoncd/pipeline
- Affected
- >=1.0.0 <1.0.2 · >=1.1.0 <1.3.4 · >=1.4.0 <1.6.2 · >=1.7.0 <1.9.3 · >=1.10.0 <1.11.1
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Tekton Pipelines has VerificationPolicy regex pattern bypass via substring matching in github.com/tektoncd/pipeline
- Affected
- >=0.43.0 <1.0.2 · >=1.1.0 <1.3.4 · >=1.4.0 <1.6.2 · >=1.7.0 <1.9.3 · >=1.10.0 <1.11.1
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Tekton Pipelines HTTP resolver denial of service via memory exhaustion in github.com/tektoncd/pipeline
- Affected
- >=1.0.0 <1.0.2 · >=1.1.0 <1.3.4 · >=1.4.0 <1.6.2 · >=1.7.0 <1.9.3 · >=1.10.0 <1.11.1
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Tekton Pipelines git resolver revision parameter argument injection in github.com/tektoncd/pipeline
- Affected
- >=1.0.0 <1.0.2 · >=1.1.0 <1.3.4 · >=1.4.0 <1.6.2 · >=1.7.0 <1.9.3 · >=1.10.0 <1.11.1
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Tekton Pipeline: Git Resolver Unsanitized Revision Parameter Enables git Argument Injection Leading to RCE
- Affected
- >=1.10.0 <1.11.1 · >=1.7.0 <1.9.3 · >=1.4.0 <1.6.2 · >=1.2.0 <1.3.4 · >=1.0.0 <1.0.2
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Tekton Pipelines: HTTP Resolver Unbounded Response Body Read Enables Denial of Service via Memory Exhaustion
- Affected
- >=1.10.0 <1.11.1 · >=1.0.0 <1.0.2 · >=1.2.0 <1.3.4 · >=1.4.0 <1.6.2 · >=1.7.0 <1.9.3
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Tekton Pipelines: VolumeMount path restriction bypass via missing filepath.Clean in /tekton/ check
- Affected
- >=1.10.0 <1.11.1 · >=1.7.0 <1.9.3 · >=1.4.0 <1.6.2 · >=1.2.0 <1.3.4 · >=1.0.0 <1.0.2
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Tekton Pipelines: Git resolver API mode leaks system-configured API token to user-controlled serverURL
- Affected
- >=1.0.0 <1.0.2 · >=1.2.0 <1.3.4 · >=1.4.0 <1.6.2 · >=1.7.0 <1.9.3 · >=1.10.0 <1.11.1
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Tekton Pipelines has VerificationPolicy regex pattern bypass via substring matching
- Affected
- >=0.43.0 <1.0.2 · >=1.2.0 <1.3.4 · >=1.4.0 <1.6.2 · >=1.7.0 <1.9.3 · >=1.10.0 <1.11.1
- Fixed in
- 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1
Path traversal in Tekton Pipelines git resolver in github.com/tektoncd/pipeline
- Affected
- >=1.0.0 <1.0.1 · >=1.1.0 <1.3.3 · >=1.4.0 <1.6.1 · >=1.7.0 <1.9.2 · >=1.10.0 <1.11.1
- Fixed in
- 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.11.1
Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun in github.com/tektoncd/pipeline
- Affected
- >=0.60.0 <1.0.1 · >=1.1.0 <1.3.3 · >=1.4.0 <1.6.1 · >=1.7.0 <1.9.2 · >=1.10.0 <1.10.2
- Fixed in
- 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2
Path traversal in Tekton Pipelines git resolver allows reading arbitrary files from the resolver pod
- Affected
- >=1.0.0 <1.0.1 · >=1.1.0 <1.3.3 · >=1.4.0 <1.6.1 · >=1.7.0 <1.9.2 · >=1.10.0 <1.10.2
- Fixed in
- 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2
Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun
- Affected
- >=0.60.0 <1.0.1 · >=1.1.0 <1.3.3 · >=1.4.0 <1.6.1 · >=1.7.0 <1.9.2 · >=1.10.0 <1.10.2
- Fixed in
- 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2
Pipelines do not validate child UIDs in github.com/tektoncd/pipeline
- Affected
- >=0.35.0
- Fixed in
- No fix released
Pipelines do not validate child UIDs
- Affected
- >=0.35.0 <=0.52.0
- Fixed in
- No fix released
Is your github.com/tektoncd/pipeline version vulnerable?
- github.com/tektoncd/pipeline 1.181 advisory in 1.18.0
- github.com/tektoncd/pipeline 1.171 advisory in 1.17.1
- github.com/tektoncd/pipeline 1.161 advisory in 1.16.0
- github.com/tektoncd/pipeline 1.151 advisory in 1.15.5
- github.com/tektoncd/pipeline 1.141 advisory in 1.14.1
- github.com/tektoncd/pipeline 1.131 advisory in 1.13.1
- github.com/tektoncd/pipeline 0.705 advisories in 0.70.0
- github.com/tektoncd/pipeline 0.695 advisories in 0.69.1
- github.com/tektoncd/pipeline 0.685 advisories in 0.68.1
- github.com/tektoncd/pipeline 0.665 advisories in 0.66.0
- github.com/tektoncd/pipeline 0.655 advisories in 0.65.7
- github.com/tektoncd/pipeline 0.645 advisories in 0.64.0
Which of your client projects still run an old github.com/tektoncd/pipeline?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.