Appearance
SEC542 / CLAUDE-GH-REPO-TRANSFER-PERMISSION
SEC542 flags shared Claude settings when permissions.allow grants blanket GitHub repository transfer authority through gh repo transfer.
Why It Matters
gh repo transfer can move repository ownership across accounts or organizations. 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 repo transfer:*)
Clean Cases
- narrower read-only grants such as
Bash(gh repo view:*) - settings files without blanket repository transfer access
- fixture-like examples under test or fixture paths
Example Trigger
json
{
"permissions": {
"allow": ["Bash(gh repo transfer:*)", "Read(*)"]
}
}Safer Example
json
{
"permissions": {
"allow": ["Bash(gh repo view:*)", "Read(*)"]
}
}How To Fix
Remove shared gh repo transfer permissions or replace them with narrower reviewed commands that keep repository transfer under explicit user control.