Skip to content

πŸ›‘οΈ Sentinel: Secure tool resolution#124

Open
acebytes wants to merge 1 commit intomainfrom
sentinel/secure-tool-resolution-7278744798030084859
Open

πŸ›‘οΈ Sentinel: Secure tool resolution#124
acebytes wants to merge 1 commit intomainfrom
sentinel/secure-tool-resolution-7278744798030084859

Conversation

@acebytes
Copy link
Copy Markdown
Contributor

🚨 Severity: LOW / Defense-in-depth

πŸ’‘ Vulnerability: The toolExists helper function used string interpolation in a /bin/bash wrapper to execute /usr/bin/which. While the input to this function was not currently user-controlled, relying on string interpolation in a shell string is an insecure pattern that could lead to command injection if the input surface area expands.

🎯 Impact: A malicious user or downstream input providing arbitrary strings (e.g., rm -rf /;) could have executed unauthorized code as the application's user identity.

πŸ”§ Fix: Refactored toolExists(_:) to execute /usr/bin/which directly as the Process.executableURL, and passed the dynamic tool input securely as an element in the Process.arguments array. This completely bypasses the shell and prevents execution of injected commands. Unnecessary standard streams were also properly mapped to FileHandle.nullDevice to prevent resource leakage.

βœ… Verification:

  • Attempted to run the test suite locally (swift / xcodebuild missing in environment, manually reviewed changes).
  • The updated code uses the correct /usr/bin/which absolute path and explicitly checks terminationStatus == 0.

PR created automatically by Jules for task 7278744798030084859 started by @acebytes

…esolution

By directly executing /usr/bin/which using a Process with an arguments
array, we eliminate the need for string interpolation in a shell wrapper,
providing a defense-in-depth measure against command injection.

Co-authored-by: acebytes <2820910+acebytes@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

πŸ‘‹ Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a πŸ‘€ emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

πŸ’‘ Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b800aa5fea

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with πŸ‘.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +189 to +191
let process = Process()
process.executableURL = URL(fileURLWithPath: "/usr/bin/which")
process.arguments = [tool]
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Set deterministic PATH for tool existence checks

This refactor invokes /usr/bin/which without setting process.environment, so it now depends on whatever PATH the app inherited. On macOS app launches (especially from Finder), PATH commonly omits /opt/homebrew/bin and /usr/local/bin, which makes toolExists("brew")/toolExists("npm") falsely return false even when tools are installed. Because resolvedPaths immediately continues when toolExists fails, probed categories can be skipped entirely and their fallback paths are never reached. Set a controlled PATH/HOME (like shell(_:) does) before process.run() to avoid this regression.

Useful? React with πŸ‘Β / πŸ‘Ž.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant