Back to skill

Security audit

Cline

Security checks for vulnerabilities and agentic risk

Overview

This skill is a small, transparent Cline wrapper, but it runs broad coding tasks through auto-approved headless execution without strong scope controls.

Install only if you trust the local Cline CLI and are comfortable with it making coding changes without per-action approval. Use it in a limited workspace, avoid secrets in prompts, and review tasks carefully before invoking it, especially for deletions, package installs, network access, or commands outside the project.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:8
Finding

Unrestricted Auto-Approved Agent Execution and Unsafe Task Interpolation

Content
View full analysis
" notes: | Use for coding, scaffolding, debugging, and multi-step plans. Keep prompts short and task-oriented. examples: - 'cline -y "Create hello.sh that prints date and uname -a."' - 'cline -y "Refactor this repo: add README and scripts folder."' ``` ### Technical Analysis The skill instructs the agent to invoke Cline with the `-y` option and an arbitrary task value. This option enables non-interactive, auto-approved operation. Consequently, commands and file modifications selected by Cline may proceed without per-operation user confirmation. The task placeholder is also embedded inside a shell-style command string: ```text cline -y "" ``` No requirement is given to pass the task as a structured process argument or to escape shell metacharacters. If the skill framework substitutes untrusted task text into this string and executes it through a shell, a task containing quote characters or shell operators could terminate the intended argument and introduce additional commands. Whether this direct injection route is exploitable depends on how the host executes the command template, but the configuration does not establish a safe argument boundary. The separate safety statement instructing the agent to ask before destructive commands does not technically enforce a control and is weakened by the unconditional use of auto-approval. ### Attack Path 1. An attacker or untrusted repository content influences the task supplied to the skill. 2. The task is substituted into `cline -y ""`. 3. One of the following execution paths occurs: - Cline interprets malicious instructions and selects unsafe commands or file modifications. - If the host uses a ...[truncated 979 chars]
Remediation
View remediation
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill exposes a very general wrapper around cline -y "<TASK>" and explicitly encourages use for coding, scaffolding, debugging, and multi-step plans without meaningful trigger constraints, approval gates, or scope limits. Because it delegates arbitrary natural-language tasks to a local CLI that may read, modify, or create repository files, this broad invocation surface can be abused for unsafe actions, prompt injection propagation, or unintended destructive changes.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.