Security audit

Proposal Service

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly clear about creating real OpenClaw proposals, but it uses very powerful database access that is broader than the task needs.

Install only if you trust the environment and are comfortable letting this skill create real pending proposals in the OpenClaw database. Prefer running the check command first, require explicit approval before create-stale-proposal, and consider replacing postgres-over-Docker access with a dedicated least-privilege database role before broader use.

A.I.G

Vulnerability Patterns

Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
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)

T05 · Unauthorized Access and Privilege Escalation

Warning

Location: scripts/proposal-service.sh:4
Finding: Database Operations Use Docker Access and the PostgreSQL Superuser
Content: View full analysis
Remediation: View remediation

SkillSpector

Vulnerability Patterns

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
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (2)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The skill explicitly enables creation of real proposals in the production-facing public.openclaw_proposals table but does not warn the user that the action has real side effects. In an agent setting, omission of a clear warning and confirmation boundary can cause unintended writes, duplicate workflow triggers, or operational noise because a user or upstream agent may treat the skill as read-only inspection rather than a mutating production action.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The SQL literals for proposal title and description are hard-coded in Spanish, and the same language constraint appears again in exception and notice messages later in the script. This imposes a specific language choice with no indication that users can select a locale or that the skill is intentionally region-specific.
Content: No source excerpt is available for this finding.