T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:48- Finding
Overly Broad Permissions Violate Least-Privilege Principles
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 48-51
Vulnerability Type: Excessive file, network, session-messaging, and delegation permissions
Risk Level: MediumVulnerable Configuration
yaml permissions: files: [read, write] network: [api] commands: [] mcp: [sessions_send, subagents]Technical Analysis
The skill declares unrestricted file read/write access, network API access, cross-session messaging through
sessions_send, and subagent delegation. Its documented purpose is strategic HR analysis and the production of policy, compliance, and governance assessments. The configuration does not specify required file paths, permitted write targets, approved API destinations, data-handling restrictions, or delegation boundaries.This violates the principle of least privilege because the declared capabilities exceed the minimum privileges demonstrated by the documented advisory workflows. Although no malicious executable code or explicit exfiltration instruction was found, these permissions create exploitable access paths if malicious or untrusted task content influences the skill.
Attack Path
- An attacker supplies a crafted HR task or strategic-context value containing instructions to inspect unrelated local information.
- The skill uses its broad
files: [read, write]permission to read sensitive files or alter files outside a narrowly defined HR workspace. - The skill uses
network: [api]orsessions_sendto transmit retrieved information or send attacker-controlled instructions to another session. - The skill invokes
subagentsto delegate additional operations, increasing the scope of the original request. - Because no path, endpoint, recipient, or delegation allowlist is defined, the resulting activity may extend beyond the legitimate HR-governance task.
This is a capability-based exploitation path. The reviewed files do not establish that the skill c ...[truncated 702 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove file access, network access, session messaging, and subagent delegation by default.
- If file access is necessary, replace unrestricted access with explicit read-only path allowlists.
- Grant write access only to designated output or audit directories, using atomic writes and preventing path traversal.
- Restrict network access to documented HTTPS endpoints, approved methods, and required request fields.
- Require explicit user approval before transmitting employee, performance, compliance, or other potentially sensitive information.
- Disable
sessions_sendunless a documented workflow requires it; otherwise, restrict recipients and message schemas. - Disable subagents unless delegation is essential. If enabled, enforce depth limits, capability restrictions, and non-inheritance of unnecessary privileges.
- Add runtime authorization checks and audit logging for every file write, outbound request, cross-session message, and subagent invocation.
- Apply data minimization and redact sensitive HR information before any authorized transmission.
