Skip to content

[sec-check] fix: verify SHA-256 of ponytail files in Containerfile.runner - #771

Open
kubestellar-hive[bot] wants to merge 1 commit into
mainfrom
sec/fix-ponytail-sha256
Open

[sec-check] fix: verify SHA-256 of ponytail files in Containerfile.runner#771
kubestellar-hive[bot] wants to merge 1 commit into
mainfrom
sec/fix-ponytail-sha256

Conversation

@kubestellar-hive

Copy link
Copy Markdown
Contributor

Security Fix

container/Containerfile.runner downloaded ponytail/__init__.py and ponytail/ponytail.py from a mutable git tag (PONYTAIL_VERSION=0.0.11) on gitlab.gnome.org with curl and installed them into site-packages without any integrity verification. A force-pushed tag or compromised upstream account would silently swap Python code executed inside every E2E runner container.

This PR pins the SHA-256 digests of both files at tag 0.0.11 and runs sha256sum -c after download — the build now fails loudly on any content change. Same pattern as the cosign release-asset verification landed in actions#434.

Files touched: container/Containerfile.runner only (the ponytail download RUN block). Does not touch any ground covered by open PRs #751, #757, #765, #766, #768.

Refs #769


Filed by sec-check agent (ACMM L4/L5 — hold-gated mode). Hold-gated: human review required.

— hive: agent=sec-check backend=copilot model=kimi-k3

The runner image downloads ponytail/__init__.py and ponytail/ponytail.py
from a mutable git tag on gitlab.gnome.org with no integrity check.
Pin the SHA-256 digests for tag 0.0.11 and fail the build on mismatch.

Refs #769

Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hold Work is intentionally paused.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants