Tekton Pipelines: HTTP Resolver Unbounded Response Body Read Enables Denial of Service via Memory Exhaustion

Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Prior to 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. This vulnerability is fixed in 1.11.1.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

未加控制的资源消耗(资源穷尽)

Tekton Pipelines 资源管理错误漏洞

Tekton Pipelines是Tekton开源的一个云原生管道。 Tekton Pipelines 1.11.1之前版本存在资源管理错误漏洞，该漏洞源于HTTP解析器的FetchHttpResource函数调用io.ReadAll(resp.Body)时未限制响应体大小，可能导致拥有创建TaskRuns或PipelineRuns权限的租户指向攻击者控制的HTTP服务器并返回超大响应体，造成tekton-pipelines-resolvers pod因内存不足被终止。

N/A

N/A