Skip to content

Rule Reference

SEC480lintai-ai-securitygovernancehardeningpreviewclaude_settingswarn

Claude settings: shared git restore permissions

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

Deterministic signal basis

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

SEC480 / CLAUDE-GIT-RESTORE-PERMISSION

SEC480 flags shared Claude settings when permissions.allow grants blanket git restore authority.

Why It Matters

git restore can discard working tree or index state. Granting Bash(git restore:*) in shared Claude settings broadens default repository mutation authority.

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

Clean Cases

These stay clean:

  • more specific commands such as Bash(git restore src/lib.rs)
  • settings files that do not grant blanket git restore
  • fixture-like examples under test or fixture paths

Example Trigger

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

Safer Example

json
{
  "permissions": {
    "allow": ["Bash(git restore src/lib.rs)", "Read(*)"]
  }
}

How To Fix

Remove shared git restore permissions or replace them with a narrower reviewed workflow that keeps restore authority under explicit user control.