lintai docs

Appearance

Rule Reference

SEC510lintai-ai-securitygovernancehardeningstableclaude_settingswarn

Claude settings: shared gh workflow run permissions

Claude settings permissions allow `Bash(gh workflow run:*)` 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 workflow dispatch authority through `permissions.allow`.

Deterministic signal basis

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

Malicious corpus
claude-settings-gh-secret-variable-workflow-permissions
Benign corpus
claude-settings-gh-secret-variable-workflow-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

SEC510 / CLAUDE-GH-WORKFLOW-RUN-PERMISSION ​

SEC510 flags shared Claude settings when permissions.allow grants blanket GitHub workflow-dispatch authority through gh workflow run.

Why It Matters ​

gh workflow run can dispatch GitHub Actions workflows remotely. In a shared committed settings file that is broader than most teams want to delegate by default.

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 workflow run:*)

Clean Cases ​

These stay clean:

  • narrower inspection grants such as Bash(gh workflow view:*)
  • settings files that do not grant blanket workflow-dispatch access
  • fixture-like examples under test or fixture paths

Example Trigger ​

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

Safer Example ​

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

How To Fix ​

Remove shared gh workflow run permissions or replace them with narrower reviewed commands that keep workflow dispatch under explicit user control.