lintai docs

Appearance

Rule Reference

SEC411lintai-ai-securitystableclaude_settingswarn

Claude settings: shared curl permissions

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

Provider
lintai-ai-security
Surface
claude_settings
Scope
per_file
Tier
stable
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 Claude settings permissions for explicit wildcard curl execution grants.

Deterministic signal basis

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

Malicious corpus
claude-settings-curl-permission
Benign corpus
claude-settings-curl-specific-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

SEC362Claude settings: wildcard Bash permissionsClaude settings permissions allow `Bash(*)` in a shared committed configclaude_settingsstable
SEC364Claude settings: bypassPermissions default modeClaude settings set `permissions.defaultMode` to `bypassPermissions` in a shared committed configclaude_settingsstable
SEC367Claude settings: wildcard WebFetch permissionsClaude settings permissions allow `WebFetch(*)` in a shared committed configclaude_settingsstable
SEC369Claude settings: wildcard Write permissionsClaude settings permissions allow `Write(*)` in a shared committed configclaude_settingsstable
SEC372Claude settings: wildcard Read permissionsClaude settings permissions allow `Read(*)` in a shared committed configclaude_settingsstable
SEC373Claude settings: wildcard Edit permissionsClaude settings permissions allow `Edit(*)` in a shared committed configclaude_settingsstable

SEC411 / CLAUDE-CURL-PERMISSION ​

SEC411 flags shared Claude settings when permissions.allow grants the exact wildcard permission Bash(curl:*).

Why It Matters ​

Granting blanket curl execution in a shared AI policy makes arbitrary network fetches part of the default team execution surface. That is a broad and easily copied permission shape for remote download workflows, even when the project does not need direct unrestricted curl access by default.

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 string Bash(curl:*)

Clean Cases ​

These stay clean:

  • more specific permissions such as Bash(curl https://example.com/install.sh)
  • settings files that do not grant curl at all
  • fixture-like examples under test or fixture paths

Example Trigger ​

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

Safer Example ​

json
{
  "permissions": {
    "allow": ["Bash(curl https://example.com/install.sh)", "Read(*)"]
  }
}

How To Fix ​

Remove shared Bash(curl:*) permissions or replace them with a narrower reviewed command pattern that keeps direct network downloads under explicit user control.