Skip to content

Rule Reference

SEC515lintai-ai-securitystableclaude_settingswarn

Claude settings: shared gh variable delete permissions

Claude settings permissions allow `Bash(gh variable delete:*)` in a shared committed config

Provider
lintai-ai-security
Surface
claude_settings
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks shared Claude settings for exact GitHub variable deletion authority through `permissions.allow`.

Deterministic signal basis

ClaudeSettingsSignals exact string detection for `Bash(gh variable delete:*)` inside permissions.allow on parsed Claude settings JSON.

Malicious corpus
claude-settings-gh-mutation-permissions
Benign corpus
claude-settings-gh-mutation-specific-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

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.allow contains the exact token Bash(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.