{{ message }}
Repository navigation
fix(rules): ignore bash scripts under RUNNER_TEMP in untrusted_checkout_exec - #461
Open
Tyagiquamar wants to merge 2 commits into
Open
Tyagiquamar wants to merge 2 commits into
Tyagiquamar wants to merge 2 commits into
Conversation
…ut_exec Steps that run shell scripts from RUNNER_TEMP are not executing checked-out workspace code. Suppress untrusted_checkout_exec when the run step references paths under RUNNER_TEMP, fixing false positives such as agentic workflow activation jobs (fixes boostsecurityio#457). Signed-off-by: Abhipsita-coder <76418226+Abhipsita-coder@users.noreply.github.com>
Tyagiquamar
force-pushed
the
fix/runner-temp-untrusted-checkout-exec
branch
from
October 12, 2026 12:49
c0b060a to
21a37e2
Compare
fproulx-boostsecurity
previously approved these changes
Oct 13, 2026
Contributor
…e list The regression fixture lives under testdata, so the workflow inventory test has to include its path. Signed-off-by: Tyagiquamar <Tyagiquamar@users.noreply.github.com>
Contributor
Author
|
Added
|
Contributor
Author
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
untrusted_checkout_execreports a finding when a workflow checks out code and later runsbash .../*.sh, even when the script lives underRUNNER_TEMP(runner-provisioned tooling), not the checked-out workspace. See #457.Root cause
The rule matches any
.shinvocation in run steps after an untrusted checkout. It does not distinguish workspace paths from\/\paths.Solution
Add a guard so run steps whose script path references
RUNNER_TEMPare excluded fromuntrusted_checkout_execcommand matching. Document the behavior in the rule page.Tests
Docker
golang:1.26-bookworm:go test ./scanner -run TestRunnerTempScriptNotFlaggedAsUntrustedCheckoutExec -count=1(pass)Issue
Fixes #457
Compatibility
No API changes. Narrows findings (fewer false positives) for workflows that execute scripts from
RUNNER_TEMP.