Git worktree directories created with chmod 777 (CWE-732)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Summary
When StackStorm creates git worktree directories for pack content versioning, it sets the permissions to 777 (world-readable, world-writable, world-executable). This allows any user on the system to read or tamper with action code before it executes.
Affected File
st2common/st2common/runners/base.py (lines 385-387)
# Make sure system / action runner user can access that directory
args = ["chmod", "777", worktree_path]
cmd = list2cmdline(args)
run_command(cmd=cmd, shell=True)
This also unnecessarily uses shell=True for a simple chmod operation.
Impact
The worktree directory contains the action code that will be executed by the action runner. With 777 permissions:
-
Code tampering: Any local user can modify the action scripts in the worktree between creation and execution, achieving arbitrary code execution in the context of the StackStorm action runner.
-
Information disclosure: Any local user can read the action code, which may contain embedded configuration, API endpoints, or logic that should not be broadly accessible.
-
Race condition: Since the worktree is created and then permissions are set in a separate step, there is a window where the directory exists with its original permissions before being opened up.
Recommended Fix
Use the minimum necessary permissions. The directory only needs to be accessible by the StackStorm system user and the action runner user:
# Use 750 (owner: rwx, group: r-x, other: none) or 770 if group write is needed
args = ["chmod", "750", worktree_path]
Or better, set ownership and permissions atomically:
import os
import stat
os.chmod(worktree_path, stat.S_IRWXU | stat.S_IRGRP | stat.S_IXGRP) # 750
This also eliminates the need for shell=True and the subprocess call entirely.
References
- CWE-732: Incorrect Permission Assignment for Critical Resource
- Discovered via manual code review
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with st2common/st2common/runners/base.py at lines 385-387 and trace how the git worktree path is created and passed to chmod. Verify the resulting permissions and command behavior for a worktree, including the absence of shell=True. Done when worktree access is limited to the required users without exposing action code to other local users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100