Repository navigation
Security: constrain repo-controlled file paths and redact design context - #1
Merged
Merged
Conversation
…rdening Close the remaining review findings by keeping design/report IO inside the repo, stopping dry-run from launching cloud agents or forwarding GITHUB_TOKEN, and requiring CLI flags to enable GitHub issues. Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
Security hardening for repository-controlled design/context/report paths. Adds tests for traversal, absolute paths, symlink escapes, private-key redaction, and protected output writes, plus a GitHub Actions build/test workflow.
Status: DRAFT / NOT VERIFIED. GitHub reports no workflow runs or commit statuses for the latest checked commit. Local checkout was unavailable, so tests have not been executed. Current report writes intentionally refuse to overwrite existing files (behaviour change). There remains a potential TOCTOU race involving symlinked parent directories; a stronger directory-handle/sandbox solution is required for hostile concurrent filesystem mutation. Additional config-controlled and scanner reads still require comprehensive audit. Do not merge or mark the vulnerability resolved until CI passes and these issues are reviewed.