lintai docs

Appearance

Rule Reference

SEC410lintai-ai-securitygovernancehardeningpreviewclaude_settingswarn

Claude settings: shared git ls-remote permissions

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

governancesidecar lane
claudesurface preset

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Checks shared Claude settings permissions for wildcard remote repository inspection grants.

Deterministic signal basis

ClaudeSettingsSignals exact string detection for `Bash(git ls-remote:*)` inside permissions.allow on parsed Claude settings JSON.

Malicious corpus
claude-settings-git-ls-remote-permission
Benign corpus
claude-settings-git-ls-remote-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

SEC385Claude settings: shared git push permissionsClaude settings permissions allow `Bash(git push)` in a shared committed configgovernancehardeningclaude_settings
SEC386Claude settings: shared git checkout permissionsClaude settings permissions allow `Bash(git checkout:*)` in a shared committed configgovernancehardeningclaude_settings
SEC387Claude settings: shared git commit permissionsClaude settings permissions allow `Bash(git commit:*)` in a shared committed configgovernancehardeningclaude_settings
SEC388Claude settings: shared git stash permissionsClaude settings permissions allow `Bash(git stash:*)` in a shared committed configgovernancehardeningclaude_settings
SEC399Claude settings: shared npx Bash permissionsClaude settings permissions allow `Bash(npx ...)` in a shared committed configgovernancehardeningclaude_settings
SEC406Claude settings: shared git add permissionsClaude settings permissions allow `Bash(git add:*)` in a shared committed configgovernancehardeningclaude_settings

SEC410 / CLAUDE-GIT-LS-REMOTE-PERMISSION ​

SEC410 flags shared Claude settings when permissions.allow grants blanket git ls-remote authority.

Why It Matters ​

git ls-remote:* lets shared AI settings probe remote repository state generically. In committed team config that can normalize remote repository inspection without forcing narrower reviewed commands.

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 ls-remote:*)

Clean Cases ​

These stay clean:

  • more specific commands such as Bash(git ls-remote origin)
  • settings files that do not grant blanket git ls-remote
  • fixture-like examples under test or fixture paths

Example Trigger ​

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

Safer Example ​

json
{
  "permissions": {
    "allow": ["Bash(git ls-remote origin)", "Read(*)"]
  }
}

How To Fix ​

Remove shared git ls-remote permissions or replace them with a narrower reviewed workflow that keeps remote repository inspection under explicit user control.