Back to skill

Security audit

Seasonal Planting Guide

Security checks for vulnerabilities and agentic risk

Overview

The planting guide is purpose-aligned, but its export feature can overwrite broad home or temporary-directory paths despite stronger safety claims.

Install only if you are comfortable with a local gardening tool that writes a custom plant database and can export markdown files. Until fixed, avoid using --export with important existing files, dotfiles, or broad home-directory paths; prefer a dedicated new file under ~/.openclaw/workspace/.

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
scripts/seasonal_planting.py:418
Finding

Unsafe Export Path Validation Allows Unauthorized File Overwrites

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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 (2)

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The top-level docstring frames the script as a guide that provides planting schedules, which implies an informational lookup tool. However, the implemented commands include mutating persistent state via add and writing user-chosen files via export_calendar, which are materially different side effects not reflected in that documentation.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

This code file supports the add command, which persists user-supplied data to ~/.openclaw/workspace/planting_calendar.json via save_db, but the top-level usage text only describes the command and does not disclose that it writes to disk. Under the code-file warning rule, file writes should have some visible disclosure; the success print happens after the write and does not serve as advance notice.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.