T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:28- Finding
Overbroad Access to Agent Profile and Operational Metadata
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 28–36
Vulnerability Type: T05: Unauthorized Access and Privilege Escalation
Risk Level: MediumRelevant Code:
markdown ### Step 1 — Read Agent Mission Read the agent's `SOUL.md`. Extract: - **Ecom platform** (Shopify, WooCommerce, Magento, custom, marketplace) - **Core workflows the agent automates** (e.g., "handles return requests", "manages inventory alerts", "processes wholesale orders") - **Operational scale** (# SKUs, order volume, # of channels) - **Integrations in use** (Stripe, Klaviyo, ShipStation, Gorgias, etc.) - **Installed skills** (to avoid re-recommending)Technical Analysis
The skill instructs the agent to read
SOUL.mdand collect a broad operational profile, including business scale, integrations, automated workflows, and installed capabilities. Reading this information is not strictly necessary for a basic public skill-catalog search, and the instructions do not require explicit user consent, field-level minimization, or verification that the target file is within the skill's authorized scope.This creates a least-privilege concern: invocation of a recommendation skill implicitly authorizes access to agent identity and state information that may reveal sensitive architectural or commercial details. Integration names can identify high-value systems such as payment processors, while installed skills and workflow descriptions can disclose the agent's capabilities and potential attack surface.
The reviewed file does not instruct the agent to transmit the extracted
SOUL.mddata to ClawHub. Its external requests use fixed, generic search terms, so direct data exfiltration is not established. The risk is limited to unauthorized collection and possible retention of metadata in the agent's execution context or generated reports.Attack Path
- A user or automated workflow invokes the e-commerce discovery skill to o ...[truncated 1683 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit user approval before reading
SOUL.md, and clearly enumerate the fields that will be accessed. - Prefer user-supplied inputs such as platform, operational focus, and installed skills instead of automatically reading agent identity or state files.
- Apply data minimization. Only collect attributes required for the current search; omit operational scale and integration inventory unless they materially affect compatibility.
- Validate that the resolved file path is the expected workspace-local
SOUL.md; prohibit arbitrary paths, symbolic-link escapes, and traversal outside the authorized workspace. - Do not copy raw
SOUL.mdcontent into generated reports. Persist only the minimum conclusions needed to explain recommendations. - Define access controls and retention limits for files written under
memory/reports/, especially when reports mention integrations or operational details. - Add an explicit prohibition against including profile data in ClawHub queries or sending it to any other external endpoint.
- Record which fields were accessed and allow the user to review or redact them before recommendation generation.
- Require explicit user approval before reading
