Objective
Fix the code injection vulnerability (CVE-severity) in .github/workflows/create-branch.yml where unsanitized user input is used in bash scripts.
Context
Poutine identified 2 critical injection points where github.event.inputs.name is used directly in bash scripts without proper sanitization. This is a critical security risk that could allow arbitrary code execution.
Related to discussion #3058
Approach
- Locate the injection points in
.github/workflows/create-branch.yml
- Sanitize
github.event.inputs.name before use in bash scripts
- Use proper quoting and input validation
- Consider using GitHub Actions expressions instead of bash variables where possible
Files to Modify
.github/workflows/create-branch.yml
Acceptance Criteria
Security Impact
HIGH: This is a critical security vulnerability that could allow malicious users to execute arbitrary code in workflow context.
Related to #3058
AI generated by Plan Command for discussion #3058
Objective
Fix the code injection vulnerability (CVE-severity) in
.github/workflows/create-branch.ymlwhere unsanitized user input is used in bash scripts.Context
Poutine identified 2 critical injection points where
github.event.inputs.nameis used directly in bash scripts without proper sanitization. This is a critical security risk that could allow arbitrary code execution.Related to discussion #3058
Approach
.github/workflows/create-branch.ymlgithub.event.inputs.namebefore use in bash scriptsFiles to Modify
.github/workflows/create-branch.ymlAcceptance Criteria
github.event.inputs.nameis properly sanitizedSecurity Impact
HIGH: This is a critical security vulnerability that could allow malicious users to execute arbitrary code in workflow context.
Related to #3058