ClawHub
Back to skill

Security audit

SP Analysis in PL/SQL Package

Security checks for vulnerabilities and agentic risk

Overview

This skill is a read-only Oracle stored procedure analysis helper, with no evidence of hidden execution, persistence, credential access, or data exfiltration.

Install only if you are comfortable letting the agent read the SQL package files you provide, and review generated procedure names and line references carefully because the included example shows a target-name consistency error.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (2)

Vague Triggers

Medium
Confidence
92% confidence
Finding
The skill is designed to act on an SP name taken from the chatbox and attached package content, which is a broad activation/input model driven by arbitrary user input. In an analysis skill, this can expand the scope of files and procedures the agent inspects or reports on without tight constraints, increasing the risk of unintended data exposure, prompt abuse, or misuse on sensitive SQL packages.

Intent-Code Divergence

Medium
Confidence
95% confidence
Finding
The example prompt asks for analysis of `get_hours()`, but the detailed section analyzes `get_date()` instead, demonstrating the skill can drift from the user-specified target procedure. In a code-analysis skill, this can mislead users into making decisions based on the wrong stored procedure, omitting relevant dependencies or data flows and undermining trust in the analysis output.

Static analysis

No suspicious patterns detected.