Appearance
SEC514 / CLAUDE-GH-SECRET-DELETE-PERMISSION
SEC514 flags shared Claude settings when permissions.allow grants blanket GitHub secret deletion authority through gh secret delete.
Why It Matters
gh secret delete can remove repository, environment, or organization secrets. 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 secret delete:*)
Clean Cases
- narrower read-only grants such as
Bash(gh secret list:*) - settings files without blanket secret deletion access
- fixture-like examples under test or fixture paths
Example Trigger
json
{
"permissions": {
"allow": ["Bash(gh secret delete:*)", "Read(*)"]
}
}Safer Example
json
{
"permissions": {
"allow": ["Bash(gh secret list:*)", "Read(*)"]
}
}How To Fix
Remove shared gh secret delete permissions or replace them with narrower reviewed commands that keep secret deletion under explicit user control.