CVE intelligence and bounded remediation

CVE-2023-37264 — Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines

Medium CVSS 4.3

Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Starting in version 0.35.0, pipelines do not validate child UIDs, which means that a user that has access to create TaskRuns can create their own Tasks that the Pipelines controller will accept as the child Task. While the software stores and validates the PipelineRun's (api version, kind, name, uid) in the child Run's OwnerReference, it only store (api version, kind, name) in the ChildStatusReference. This means that if a client had access to create TaskRuns on a cluster, they could create a child TaskRun for a pipeline with the same name + owner reference, and the Pipeline controller picks it up as if it was the original TaskRun. This is problematic since it can let users modify the config of Pipelines at runtime, which violates SLSA L2 Service Generated / Non-falsifiable requirements. This issue can be used to trick the Pipeline controller into associating unrelated Runs to the Pipeline, feeding its data through the rest of the Pipeline. This requires access to create TaskRuns, so impact may vary depending on one Tekton setup. If users already have unrestricted access to create any Task/P…

Severity
Medium
CVSS
4.3 (3.1)
Published
2023-07-07
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-345

Affected products

  • linuxfoundation / tekton_pipelines

Matched remediation archetype

Supply-chain, dependency, build, and update integrity

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
  • Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
  • Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.

Remediate safely

  • Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
  • Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
  • Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.