Skip to content

[sec-check] fix: label-enforcement.yml pin reusable workflow to full SHA - #126

Open
kubestellar-hive[bot] wants to merge 1 commit into
mainfrom
sec/fix-label-enforcement-sha
Open

[sec-check] fix: label-enforcement.yml pin reusable workflow to full SHA#126
kubestellar-hive[bot] wants to merge 1 commit into
mainfrom
sec/fix-label-enforcement-sha

Conversation

@kubestellar-hive

Copy link
Copy Markdown

Security Fix

Pins the projectbluefin/actions/.github/workflows/reusable-design-enforcement.yml call in .github/workflows/label-enforcement.yml to the full 40-character SHA (67d4cfb597e331448e31047a380439bdeee91865) instead of the 7-character short SHA. Because the call uses secrets: inherit, ref integrity matters: short SHAs are collision-feasible.

Fixes #122


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 copilot=1.0.59

The reusable-design-enforcement call was pinned to a 7-character short
SHA with secrets: inherit. Short SHAs are collision-feasible; use the
full 40-char SHA of the same commit.

Fixes #122

Signed-off-by: kubestellar-hive[bot] <280983584+kubestellar-hive[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. security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[sec-check] label-enforcement.yml: reusable workflow pinned to short SHA with secrets: inherit

0 participants