Tekton Pipelines: HTTP Resolver Unbounded Response Body Read Enables Denial of Service via Memory Exhaustion
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.3.41.6.21.9.3Tekton 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 HTTP resolver's FetchHttpResource function calls io.ReadAll(resp.Body) with no response body size limit. Any tenant with permission to create TaskRuns or PipelineRuns that reference the HTTP resolver can point it at an attacker-controlled HTTP server that returns a very large response body within the 1-minute timeout window, causing the tekton-pipelines-resolvers pod to be OOM-killed by Kubernetes. Because all resolver types (Git, Hub, Bundle, Cluster, HTTP) run in the same pod, crashing this pod denies resolution service to the entire cluster. Repeated exploitation causes a sustained crash loop. The same vulnerable code path is reached by both the deprecated pkg/resolution/resolver/http and the current pkg/remoteresolution/resolver/http implementations. 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 HTTP resolver reads response bodies without a size limit. A tenant permitted to create TaskRuns or PipelineRuns can reference an attacker-controlled HTTP server that returns a large response, causing the shared resolvers pod to be OOM-killed. Repeated requests can sustain a crash loop and deny resolution service across the cluster; no user interaction is required.
Operators running Tekton Pipelines or the Go package github.com/tektoncd/pipeline from version 1.0.0 up to, but not including, the applicable fixed version should check their deployments.