Skip to content
11 changes: 11 additions & 0 deletions config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
version: "1"
allowed_remote_resources:
- "https://raw.githubusercontent.com/fullsend-ai/fullsend/"
- "https://raw.githubusercontent.com/fullsend-ai/agents/"
Comment on lines +2 to +4

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remediation recommended

3. Overbroad remote allowlist 🐞 Bug ⛨ Security

config.yaml allowlists entire raw.githubusercontent.com prefixes for fullsend-ai/fullsend and
fullsend-ai/agents, allowing fullsend to fetch any file at any ref under those repos. Because
pre/post scripts run on the GitHub Actions runner (not just in the sandbox) and functional tests run
in pull_request_target with secrets, this unnecessarily expands runner-side remote code-fetch
surface.
Agent Prompt
## Issue description
`allowed_remote_resources` is currently a broad prefix allowlist that can permit fetching arbitrary content from entire repos/refs.

## Issue Context
Functional tests run in `pull_request_target` and pass secrets into the run; the agent pipeline executes pre/post scripts on the runner.

## Fix Focus Areas
- config.yaml[1-4]
- .github/workflows/functional-tests.yml[3-6]
- .github/workflows/functional-tests.yml[245-255]

## Proposed fix
1. Narrow the allowlist to the minimal required subpaths (e.g., only the specific directories/files that fullsend actually needs to fetch).
2. Prefer pinning to immutable refs (commit SHA or a specific release tag path) instead of allowing any ref.
3. If feasible, generate/overwrite the allowlist in the workflow from a trusted base-branch source (or validate the PR’s config) so PRs can’t broaden it in secret-bearing `pull_request_target` runs.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

agents:
- source: harness/triage.yaml
- source: harness/code.yaml
- source: harness/fix.yaml
- source: harness/review.yaml
- source: harness/retro.yaml
- source: harness/prioritize.yaml
Comment thread
qodo-code-review[bot] marked this conversation as resolved.
Resolved
Loading