Skip to content

Rule Reference

SEC503lintai-ai-securitystableclaude_settingswarn

Claude settings: shared gh issue create permissions

Claude settings permissions allow `Bash(gh issue create:*)` 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 issue creation authority through `permissions.allow`.

Deterministic signal basis

ClaudeSettingsSignals exact string detection for `Bash(gh issue create:*)` 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

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