lintai docs

Appearance

Rule Reference

SEC463lintai-ai-securitystablemarkdownwarn

AI markdown: `Bash(sudo:*)` tool grant

AI-native markdown frontmatter grants `Bash(sudo:*)` authority

Provider
lintai-ai-security
Surface
markdown
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
skillsmembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks AI-native frontmatter for explicit wildcard sudo grants in shared allowed-tools policy.

Deterministic signal basis

MarkdownSignals exact frontmatter token detection for `Bash(sudo:*)` inside allowed-tools or allowed_tools.

Malicious corpus
skill-sudo-allowed-tools
Benign corpus
skill-sudo-allowed-tools-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

SEC352AI markdown: unscoped Bash tool grantAI-native markdown frontmatter grants unscoped Bash tool accessmarkdownstable
SEC417AI markdown: unpinned pip git installAI-native markdown installs Python packages from an unpinned `git+https://` sourcemarkdownstable
SEC428AI markdown: unsafe Read path grantAI-native markdown frontmatter grants `Read(...)` over an unsafe repo-external pathmarkdownstable
SEC429AI markdown: unsafe Write path grantAI-native markdown frontmatter grants `Write(...)` over an unsafe repo-external pathmarkdownstable
SEC430AI markdown: unsafe Edit path grantAI-native markdown frontmatter grants `Edit(...)` over an unsafe repo-external pathmarkdownstable
SEC431AI markdown: unsafe Glob path grantAI-native markdown frontmatter grants `Glob(...)` over an unsafe repo-external pathmarkdownstable

SEC463 / MD-SUDO-ALLOWED-TOOLS ​

SEC463 flags AI-native markdown when shared frontmatter grants exact Bash(sudo:*) authority through allowed-tools or allowed_tools.

Why It Matters ​

Bash(sudo:*) gives shared instructions blanket privilege-escalation authority. In AI-native frontmatter, that turns privileged execution into a default team-wide capability instead of a reviewed narrow workflow.

What Triggers It ​

  • AI-native markdown surface with frontmatter
  • allowed-tools or allowed_tools contains exact Bash(sudo:*)

The finding points to the exact frontmatter token.

What Does Not Trigger It ​

  • more specific reviewed commands such as Bash(sudo apt-get update)
  • fixture-like frontmatter paths used only for tests
  • frontmatter without Bash(sudo:*)

Example ​

Bad:

yaml
allowed-tools: Bash(sudo:*), Read

Better:

yaml
allowed-tools: Bash(sudo apt-get update), Read

Remediation ​

Review whether shared Bash(sudo:*) access is really needed. Prefer a narrower reviewed privileged workflow instead of a blanket team-wide sudo grant.