lintai docs

Appearance

Rule Reference

SEC502lintai-ai-securitygovernancehardeningstableclaude_settingswarn

Claude settings: shared gh api POST permissions

Claude settings permissions allow `Bash(gh api --method POST:*)` in a shared committed config

Public lane
governance
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
claude_settings
Tier
stable
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.

governancesidecar lane
claudesurface preset

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Checks shared Claude settings for exact GitHub API POST mutation authority through `permissions.allow`.

Deterministic signal basis

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

SEC362Claude settings: wildcard Bash permissionsClaude settings permissions allow `Bash(*)` in a shared committed configgovernancehardeningclaude_settings
SEC364Claude settings: bypassPermissions default modeClaude settings set `permissions.defaultMode` to `bypassPermissions` in a shared committed configgovernancehardeningclaude_settings
SEC367Claude settings: wildcard WebFetch permissionsClaude settings permissions allow `WebFetch(*)` in a shared committed configgovernancehardeningclaude_settings
SEC369Claude settings: wildcard Write permissionsClaude settings permissions allow `Write(*)` in a shared committed configgovernancehardeningclaude_settings
SEC372Claude settings: wildcard Read permissionsClaude settings permissions allow `Read(*)` in a shared committed configgovernancehardeningclaude_settings
SEC373Claude settings: wildcard Edit permissionsClaude settings permissions allow `Edit(*)` in a shared committed configgovernancehardeningclaude_settings

SEC502 / CLAUDE-GH-API-POST-PERMISSION ​

SEC502 flags shared Claude settings when permissions.allow grants blanket GitHub CLI API mutation authority through gh api --method POST.

Why It Matters ​

gh api --method POST is a generic remote mutation path against GitHub resources. In shared committed settings that is broader than most teams actually need and is harder to review than narrower workflow-specific subcommands.

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 api --method POST:*)

Clean Cases ​

These stay clean:

  • more specific read-only API calls such as Bash(gh api --method GET:*)
  • settings files that do not grant blanket POST mutation access
  • fixture-like examples under test or fixture paths

Example Trigger ​

json
{
  "permissions": {
    "allow": ["Bash(gh api --method POST:*)", "Read(*)"]
  }
}

Safer Example ​

json
{
  "permissions": {
    "allow": ["Bash(gh api --method GET:*)", "Read(*)"]
  }
}

How To Fix ​

Remove shared gh api --method POST permissions or replace them with narrower reviewed subcommands that keep remote GitHub mutations under explicit user control.