T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:5- Finding
Excessive Shell and Filesystem Permissions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 5 and 19–21; related command guidance at lines 230, 233, and 242
Vulnerability Type: Violation of least privilege through unnecessaryexec,read, andwritecapabilities
Risk Level: MediumVulnerable Code Snippet
yaml allowed-tools: read execyaml tools: - exec - read - writeRelated documentation also classifies the skill as command-enabled and directs the agent to run a network diagnostic:
markdown - 本工具为纯 Markdown 指令,无需额外 API Keymarkdown - **分类**: MD+EXEC(Markdown 指令 + 命令行执行)markdown | 网络错误 | 连接超时或不可达 | 执行ping命令测试网络连通性,检查防火墙和代理设置连接后执行ping命令测试网络连通性,检查防火墙和代理设置连接后重新执行命令,参考国内替代方案 |Technical Analysis
The skill's stated function is to conduct a conversational interview simulation, evaluate answers, and generate a scorecard. These operations do not require shell execution or local filesystem access. Nevertheless, the skill declares
exec,read, andwritecapabilities.The permission declarations are also inconsistent: the top-level
allowed-toolsfield grantsreadandexec, while the separatetoolslist additionally declareswrite. Depending on how an agent platform resolves conflicting metadata, the skill could receive broader access than a reviewer or operator expects.The documented
pingoperation does not justify general-purpose shell access. A broadexeccapability is substantially more powerful than a constrained connectivity check. Because the skill accepts user-controlled interview responses and pasted resume content, unnecessarily exposing privileged tools increases the consequences of prompt injection embedded in that content.No direct instruction to execute an attacker-controlled command was identified. This finding concerns excessive capability and the resulting attack surface rather than confirmed malicious command execution.
Attack Pa
...[truncated 1320 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
exec,read, andwritefrom the skill metadata because the interview workflow can operate entirely through language-model interaction. - If a tool is genuinely required in a future version, grant only the specific capability needed and enforce strict path, command, argument, and network-destination allowlists.
- Make all permission declarations consistent; do not maintain conflicting
allowed-toolsandtoolslists. - Remove the
pingrecommendation. Report connectivity failures descriptively or rely on platform-controlled health checks rather than general-purpose command execution. - Treat resumes and interview responses as untrusted data. Explicitly instruct the agent not to follow commands or operational instructions embedded in user-provided documents.
- Enforce runtime confirmation and sandboxing for any future filesystem or shell operation.
- Add automated validation that rejects undeclared, contradictory, or unnecessary tool permissions during packaging.
- Remove
