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.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1, the Tekton Pipelines git resolver in API mode sends the system-configured Git API token to a user-controlled serverURL when the user omits the token parameter. A tenant with TaskRun or PipelineRun create permission can exfiltrate the shared API token (GitHub PAT, GitLab token, etc.) by pointing serverURL to an attacker-controlled endpoint. Versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 fix the issue.
Weakness
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tekton_pipelines | Linuxfoundation | 1.0.0 (including) | 1.10.0 (including) |
| Red Hat OpenShift Builds 1.7.3 | RedHat | openshift-builds/openshift-builds-controller-rhel9:1780373846 | * |
| Red Hat OpenShift Builds 1.7.3 | RedHat | openshift-builds/openshift-builds-git-cloner-rhel9:1780374151 | * |
| Red Hat OpenShift Builds 1.7.3 | RedHat | openshift-builds/openshift-builds-image-processing-rhel9:1780373835 | * |
| Red Hat OpenShift Builds 1.7.3 | RedHat | openshift-builds/openshift-builds-rhel9-operator:1780480839 | * |
| Red Hat OpenShift Builds 1.7.3 | RedHat | openshift-builds/openshift-builds-waiters-rhel9:1780374228 | * |
| Red Hat OpenShift Builds 1.7.3 | RedHat | openshift-builds/openshift-builds-webhook-rhel9:1780374084 | * |
| Red Hat OpenShift Pipelines 1.21 | RedHat | serve-tkn-cli-1-21-serve-tkn-cli-1.21.1 | * |
Potential Mitigations
- Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/12.html
- https://cwe.mitre.org/data/definitions/217.html
- https://cwe.mitre.org/data/definitions/612.html
- https://cwe.mitre.org/data/definitions/613.html
- https://cwe.mitre.org/data/definitions/618.html
- https://cwe.mitre.org/data/definitions/619.html
- https://cwe.mitre.org/data/definitions/621.html
- https://cwe.mitre.org/data/definitions/622.html
- https://cwe.mitre.org/data/definitions/623.html