Skip to content

Rule Reference

SEC408lintai-ai-securitygovernancehardeningpreviewclaude_settingswarn

Claude settings: shared gh pr permissions

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

Public lane
governance
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
claude_settings
Tier
preview
Severity
warn
Confidence
high
Detection
structural
Remediation
message only
How to read this lane

Shared authority and workflow policy review.

How to read this category

Least-privilege, provenance, or operational hygiene signal.

Activation Model

Preset Activation

These presets explain where this rule appears in the product experience.

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Checks shared committed Claude settings for exact `Bash(gh pr:*)` authority.

Deterministic signal basis

ClaudeSettingsSignals exact permission detection for `Bash(gh pr:*)` entries inside permissions.allow.

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

Structural preview rule; deterministic today, but the preview contract may still evolve.

Nearby Signals

Related Rules

SEC408 / CLAUDE-GH-PR-PERMISSION

SEC408 flags shared Claude settings when permissions.allow grants blanket gh pr authority.

Why It Matters

gh pr:* bundles broad pull-request operations behind one shared permission token. In committed team settings that can normalize remote PR actions without forcing a narrower reviewed subcommand set.

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 pr:*)

Clean Cases

These stay clean:

  • more specific commands such as Bash(gh pr diff:*)
  • settings files that do not grant blanket gh pr
  • fixture-like examples under test or fixture paths

Example Trigger

json
{
  "permissions": {
    "allow": ["Bash(gh pr:*)", "Read(*)"]
  }
}

Safer Example

json
{
  "permissions": {
    "allow": ["Bash(gh pr diff:*)", "Read(*)"]
  }
}

How To Fix

Remove shared gh pr permissions or replace them with narrower reviewed subcommands that keep pull-request operations under explicit user control.