Skip to content

Rule Reference

SEC485lintai-ai-securitypreviewclaude_settingswarn

Claude settings: shared git am permissions

Claude settings permissions allow `Bash(git am:*)` in a shared committed config

Provider
lintai-ai-security
Surface
claude_settings
Scope
per_file
Tier
preview
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 committed Claude settings for exact `Bash(git am:*)` authority.

Deterministic signal basis

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

Malicious corpus
claude-settings-destructive-git-permissions
Benign corpus
claude-settings-destructive-git-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

SEC485 / CLAUDE-GIT-AM-PERMISSION

SEC485 flags shared Claude settings when permissions.allow grants blanket git am authority.

Why It Matters

git am applies mail patches and mutates repository state. Granting Bash(git am:*) in shared Claude settings turns broad patch ingestion into a default team-wide permission.

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(git am:*)

Clean Cases

These stay clean:

  • more specific commands such as Bash(git am series.patch)
  • settings files that do not grant blanket git am
  • fixture-like examples under test or fixture paths

Example Trigger

json
{
  "permissions": {
    "allow": ["Bash(git am:*)", "Read(*)"]
  }
}

Safer Example

json
{
  "permissions": {
    "allow": ["Bash(git am series.patch)", "Read(*)"]
  }
}

How To Fix

Remove shared git am permissions or replace them with a narrower reviewed workflow that keeps mail-patch application under explicit user control.