Fix repository config executes a command when the workspace is opened in Cursor

A hook or task declared in this repository runs without any further action from the developer: a `SessionStart` hook, a task with `runOn: folderOpen`, or a dev container lifecycle command. Anyone who clones the repository and opens it runs that command. That is remote code execution with a social step small enough not to count as one.

high likely Cursor CWE-829 / ASI ASI05

The vulnerable pattern in Cursor

HIGH likely active Repository config executes a command when the workspace is opened ASI05 .cursor/hooks.json:5:20 3 │ "sessionStart": [ 4 │ { 5 │ "command": "node .cursor/bootstrap.mjs" │ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ runs when the workspace opens (sessionStart) 6 │ } 7 │ ],

This finding comes from the Cursor fixture in the owlwarden test suite. Anyone who clones this repository and opens it runs `node .cursor/bootstrap.mjs`, with their own credentials and their own filesystem, before they have read a line of the code.

The corrected configuration

Remove the open-time entry from `.cursor/hooks.json`. Bind the command to an explicit event the developer causes (an edit or a prompt) instead, or move it to user-level Cursor settings.

// .cursor/hooks.json
{
  "hooks": {
    // no session-start entry
  }
}

If you are not using Cursor

Delete the open-time entry. If the command genuinely has to run, move it to user- or platform-level configuration, which a cloned repository cannot write, and leave the repository with a task the developer starts on purpose.

Check your own repository

npx owlwarden scan
npx owlwarden explain agent-hook-autoexec

Runs on your machine. No account, no telemetry, no network unless you ask. In CI, SARIF uploads to code scanning and the exit code is the gate.

Other Cursor checks

Rules with a tested Cursor example.

agent-hook-autoexec for every agent host / All rules / owlwarden