T05 · Unauthorized Access and Privilege Escalation
- Location
claw.json:8- Finding
Unnecessary Network Permission Violates Least Privilege
- Content
View full analysis
Vulnerability Details
File Location:
claw.json, lines 8–11
Vulnerability Type: Excessive runtime permission
Risk Level: MediumVulnerable Code
json "permissions": [ "filesystem", "network" ],Technical Analysis
The Skill requests unrestricted network access even though its documented ERP-analysis operations process user-provided data locally. Neither
SKILL.mdnorinstructions.mddefines a feature that needs to send network requests or retrieve remote resources. The URLs inSKILL.mdare informational references, and the embedded Python code contains no network client implementation.The filesystem permission is consistent with accepting file paths and offering data exports. However, the network permission is not supported by the documented functionality and therefore violates the principle of least privilege. Although the current implementation contains no outbound request or data-exfiltration code, this unnecessary capability could become an outbound communication channel if the Skill's behavior were later compromised or influenced by untrusted input.
Attack Path
- A user activates the Skill, and the runtime grants the permissions declared in
claw.json. - The Skill receives network access despite having no legitimate network-dependent feature.
- A future compromised implementation, malicious update, or successfully injected behavior invokes the granted network capability.
- The malicious behavior connects to an attacker-controlled endpoint.
- Data accessible during the Skill session could then be transmitted externally.
The current reviewed files do not implement steps 3–5; this finding concerns the exposed capability and resulting reduction in defense in depth rather than an observed active exfiltration mechanism.
Impact Assessment
The unnecessary permission expands the Skill's effective access from local data processing to outbound network communicati ...[truncated 328 chars]
- A user activates the Skill, and the runtime grants the permissions declared in
- Remediation
View remediation
Remediation Suggestions
- Remove
"network"from thepermissionsarray because the currently documented functionality does not require it. - Retain only the minimum filesystem capabilities needed to read user-selected input files and write explicitly requested exports.
- If a future feature legitimately requires network access, document its purpose, destination, request method, and transmitted fields before enabling it.
- Where the runtime supports scoped permissions, restrict connectivity to an explicit allowlist of trusted hosts rather than granting unrestricted network access.
- Require user confirmation before transmitting project or ERP data and prevent credentials, tokens, and unrelated session data from being included.
- Add automated manifest checks that reject permissions not mapped to documented and tested functionality.
- Remove
