Skip to content

🛡️ Sentinel: [security improvement] Use direct Process execution for tool discovery#146

Open
acebytes wants to merge 1 commit intomainfrom
sentinel-fix-command-injection-toolexists-64058303321218979
Open

🛡️ Sentinel: [security improvement] Use direct Process execution for tool discovery#146
acebytes wants to merge 1 commit intomainfrom
sentinel-fix-command-injection-toolexists-64058303321218979

Conversation

@acebytes
Copy link
Copy Markdown
Contributor

💡 What: Refactored toolExists to use direct Process execution instead of interpolating strings in shell() wrapper commands.
🎯 Why: This is a defense-in-depth measure to mitigate command injection risks by avoiding shell wrapper commands with string interpolation or variables. Instead, use Process().arguments array to separate the executable and its arguments.


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

Replaced `shell()` with direct `Process` execution to prevent command injection vulnerabilities via string interpolation.

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: 2f33d14a3d

ℹ️ 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 +193
let process = Process()
process.executableURL = URL(fileURLWithPath: "/usr/bin/which")
process.arguments = [tool]
process.standardOutput = FileHandle.nullDevice
process.standardError = FileHandle.nullDevice
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 Preserve explicit PATH when checking tool availability

This refactor changed toolExists to inherit the app’s environment, but Finder/LaunchServices-launched macOS apps often have a minimal PATH (commonly missing /opt/homebrew/bin and /usr/local/bin). In that context, /usr/bin/which brew/npm/pnpm returns not found even when the tool is installed, so .probed(... requiresTool: ...) categories are skipped and cache locations are never discovered. The previous implementation avoided this by forcing a known PATH via shell().

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