Appearance
SEC503 / CLAUDE-GH-ISSUE-CREATE-PERMISSION
SEC503 flags shared Claude settings when permissions.allow grants blanket GitHub issue-creation authority.
Why It Matters
gh issue create mutates remote issue trackers. In shared committed settings that can normalize unattended issue creation instead of keeping it behind narrower, explicitly reviewed workflows.
Trigger Shape
The rule triggers only when all of these are true:
- the file is a detected Claude settings surface
- the path is not fixture-like
permissions.allowcontains the exact tokenBash(gh issue create:*)
Clean Cases
These stay clean:
- read-only issue commands such as
Bash(gh issue view:*) - settings files that do not grant blanket issue creation
- fixture-like examples under test or fixture paths
Example Trigger
json
{
"permissions": {
"allow": ["Bash(gh issue create:*)", "Read(*)"]
}
}Safer Example
json
{
"permissions": {
"allow": ["Bash(gh issue view:*)", "Read(*)"]
}
}How To Fix
Remove shared gh issue create permissions or replace them with narrower reviewed subcommands that keep GitHub issue creation under explicit user control.