T05 · Unauthorized Access and Privilege Escalation
- Location
md2html.py:25- Finding
Project Path Restriction Can Be Bypassed Through Symbolic Links
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This document-conversion skill is understandable, but it needs Review because crafted inputs could make it read unintended local files or create HTML with active content.
Install only if you trust the documents and paths being converted. Avoid using it on attacker-supplied project folders, symlinks, Markdown, HTML, or titles, and render generated HTML/PDF in an isolated viewer rather than a trusted application origin. Prefer a hardened version that resolves real paths under the project root, rejects symlinks, escapes titles, sanitizes HTML, and pins dependencies.
md2html.py:25Project Path Restriction Can Be Bypassed Through Symbolic Links
md2html.py:53Untrusted Markdown and Title Values Can Inject Active Content into Generated HTML
SKILL.md:22Dependency Installation Instructions Use Unpinned Packages Without Integrity Verification
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill advertises local file-based conversion and explicitly accepts a user-supplied path, but it does not declare any tool scope or permissions boundary for file access. That mismatch can let an agent read arbitrary local files under the guise of document conversion, increasing the risk of unintended data exposure if the skill is invoked on attacker-influenced paths.
The trigger description includes broad wording such as 'or similar document format conversion', which can cause the agent to invoke the skill in situations beyond its narrowly intended use. Over-broad activation is risky here because the skill can read local files and transform content, potentially exposing sensitive data or causing unintended file handling from loosely matched user requests.
The generated HTML document hard-codes lang="zh-CN", which imposes a specific language/locale setting on output for all users. The file does not provide an option to choose another locale or document that this is intentionally limited to a China-specific use case.
No suspicious patterns detected.