lintai docs

Appearance

Rule Reference

SEC407lintai-ai-securitypreviewclaude_settingswarn

Claude settings: shared git clone permissions

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

previewmembership
claudemembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks shared committed Claude settings for exact `Bash(git clone:*)` authority.

Deterministic signal basis

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

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

SEC361Claude settings: missing `$schema`Claude settings file is missing a top-level `$schema` referenceclaude_settingspreview
SEC363Claude settings: home-directory hook pathClaude settings hook command uses a home-directory path in a shared committed configclaude_settingspreview
SEC365Claude settings: non-HTTPS allowed HTTP hook URLClaude settings allow non-HTTPS HTTP hook URLs in a shared committed configclaude_settingspreview
SEC366Claude settings: dangerous HTTP hook host literalClaude settings allow dangerous host literals in `allowedHttpHookUrls`claude_settingspreview
SEC368Claude settings: repo-external absolute hook pathClaude settings hook command uses a repo-external absolute path in a shared committed configclaude_settingspreview
SEC381Claude settings: command hook missing `timeout`Claude settings command hook should set `timeout` in a shared committed configclaude_settingspreview

SEC407 / CLAUDE-GIT-CLONE-PERMISSION ​

SEC407 flags shared Claude settings when permissions.allow grants blanket git clone authority.

Why It Matters ​

git clone brings arbitrary remote repositories into the local execution path. Granting Bash(git clone:*) in shared Claude settings turns remote repository fetching into default team policy instead of an explicitly reviewed action.

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

Clean Cases ​

These stay clean:

  • more specific commands such as Bash(git clone https://github.com/acme/demo.git)
  • settings files that do not grant blanket git clone
  • fixture-like examples under test or fixture paths

Example Trigger ​

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

Safer Example ​

json
{
  "permissions": {
    "allow": ["Bash(git clone https://github.com/acme/demo.git)", "Read(*)"]
  }
}

How To Fix ​

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