Skip to content

Rule Reference

SEC484lintai-ai-securitypreviewclaude_settingswarn

Claude settings: shared git apply permissions

Claude settings permissions allow `Bash(git apply:*)` 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 apply:*)` authority.

Deterministic signal basis

ClaudeSettingsSignals exact permission detection for `Bash(git apply:*)` 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

SEC484 / CLAUDE-GIT-APPLY-PERMISSION

SEC484 flags shared Claude settings when permissions.allow grants blanket git apply authority.

Why It Matters

git apply can apply arbitrary patches to the working tree or index. Granting Bash(git apply:*) in shared Claude settings makes broad patch-application authority a default shared 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 apply:*)

Clean Cases

These stay clean:

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

Example Trigger

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

Safer Example

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

How To Fix

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