ClawHub
Back to skill

Security audit

Venafi TLS Protect Cloud

Security checks for vulnerabilities and agentic risk

Overview

The certificate-reading workflow is coherent, but automatic setup can execute unverified downloaded code and introduce persistent agent skills.

Review the setup before installing. Use a reviewed CLI release, approve local installation separately, and consider disabling startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1 as documented upstream. Connect only the Venafi account and permissions needed. The read workflow appears legitimate; the concern is uncontrolled setup and persistent side effects, not evidence of malicious intent. The remote installers could not be inspected.

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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The supplied command does not perform any visible Venafi TLS Protect Cloud operation. Instead, it fetches and executes an installer from cli.oomol.com, with no demonstrated connection to the declared service. This is an undeclared capability involving an inconsistent resource, not an established supporting implementation detail. The downloaded script's exact behavior cannot be determined from the supplied chunk.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
99% confidence
Finding

Piping the HTTPS installer directly into bash executes whatever content the endpoint supplies with the agent process's privileges, without a pinned version or independent integrity verification. A compromised installer endpoint or release pipeline could therefore expose accessible credentials and files or modify the system; its legitimate dependency-installation purpose and conditional use do not remove this supply-chain risk.

Content

Scanner excerpt · SKILL.md (reported line 57)May include surrounding context.

The fallback setup instructs the agent to execute downloaded installation scripts without warning about remote-code execution or system changes.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

The fallback instructs the agent to install software by executing remote scripts without requiring approval or explaining that this changes the local environment. Restricting setup to a missing-command error reduces exposure, but a read-only certificate request can still lead to consequential local code execution without informed consent.

Content

No source excerpt is available for this finding.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 78)May include surrounding context.

md
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

## Resources