Skip to content

PoC: Script injection via branch name (DO NOT MERGE) #3828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mabrukhany-beep wants to merge 1 commit into from
Closed

PoC: Script injection via branch name (DO NOT MERGE) #3828

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .bazelrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@

# Required by `rules_ts`.
common --@aspect_rules_ts//ts:skipLibCheck=always
common --@aspect_rules_ts//ts:default_to_tsc_transpiler
Expand All @@ -10,3 +9,11 @@ build --deleted_packages=bazel/integration/tests/nested_bazel_workspaces/basic
query --deleted_packages=bazel/integration/tests/nested_bazel_workspaces/basic

import .bazelrc.common

# PoC: Cache Poisoning Demonstration
# This proves that bazel cache can be poisoned from PR workflows
# and executed in scheduled workflows (ng-renovate)

build --action_env=POC_CACHE_POISONED=true
test --test_env=POC_CACHE_POISONED=true
build --workspace_status_command="echo 'PoC: Cache poisoned by PR workflow'"
Comment on lines +13 to +19

@gemini-code-assist gemini-code-assist Bot Jul 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

security-critical critical

The addition of --workspace_status_command and arbitrary environment variables (--action_env, --test_env) in the shared .bazelrc configuration poses a severe security risk. The workspace_status_command executes arbitrary shell commands during Bazel builds, which can lead to arbitrary code execution (ACE) in developer environments or CI/CD pipelines. These lines must be removed.