T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:7- Finding
Unnecessary Shell Execution Capability Violates Least Privilege
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 7-10
Vulnerability Type: Excessive tool permissions
Risk Level: Mediumyaml tools: - Read - Write - BashTechnical Analysis
The skill requests access to the
Bashtool even though its documented functionality only requires reading and writing a user profile, analyzing job descriptions, and generating text. No documented workflow requires command execution.Shell access is substantially more powerful than the capabilities needed for this task. If attacker-controlled content in a job description, resume, or screenshot successfully influences the agent's tool usage, the unnecessary shell permission could turn an instruction-injection event into local command execution. The declaration therefore violates the principle of least privilege and unnecessarily increases the consequences of agent manipulation.
Attack Path
- An attacker places adversarial instructions in a job description, resume, or recruitment screenshot.
- The user submits that content to the skill for analysis.
- The agent interprets the embedded content as operational instructions rather than untrusted data.
- Because the skill has access to
Bash, the manipulated agent attempts to execute a local command. - The command runs with the operating-system privileges and filesystem access available to the agent process.
No direct command-injection implementation was found in the audited files. This attack path depends on successful agent instruction injection, but the unnecessary capability materially increases its potential impact.
Impact Assessment
Successful exploitation could permit command execution within the security context of the agent process. Depending on the surrounding sandbox and operating-system permissions, this may expose local files, environment variables, accessible credentials, and other user data. It could also allow modification of file ...[truncated 277 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
Bashfrom the tool declaration because no documented workflow requires shell execution. - Retain only the minimum
ReadandWritecapabilities needed for profile management. - Where supported, restrict filesystem access to the dedicated profile file rather than granting general read and write access.
- Treat job descriptions, resumes, and OCR output as untrusted data and explicitly prohibit following instructions embedded in those inputs.
- Require user confirmation before performing any operation outside text analysis or profile maintenance.
- If future functionality genuinely requires a command, expose a narrowly scoped purpose-built tool instead of unrestricted shell access.
- Remove
