Appearance
SEC515 / CLAUDE-GH-VARIABLE-DELETE-PERMISSION
SEC515 flags shared Claude settings when permissions.allow grants blanket GitHub variable deletion authority through gh variable delete.
Why It Matters
gh variable delete can remove repository, environment, or organization variables. In a shared committed settings file that is broader than most teams want to delegate by default.
Trigger Shape
- the file is a detected Claude settings surface
- the path is not fixture-like
permissions.allowcontains the exact tokenBash(gh variable delete:*)
Clean Cases
- narrower read-only grants such as
Bash(gh variable list:*) - settings files without blanket variable deletion access
- fixture-like examples under test or fixture paths
Example Trigger
json
{
"permissions": {
"allow": ["Bash(gh variable delete:*)", "Read(*)"]
}
}Safer Example
json
{
"permissions": {
"allow": ["Bash(gh variable list:*)", "Read(*)"]
}
}How To Fix
Remove shared gh variable delete permissions or replace them with narrower reviewed commands that keep variable deletion under explicit user control.