T09 · Insecure Skill Coding Practices
- Location
scripts/svg2png.js:148- Finding
Unbounded SVG Processing Enables Resource-Exhaustion Denial of Service
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill coherently generates infographic files, with expected local rendering behavior and no evidence of hidden data access, persistence, or exfiltration.
Install only if you are comfortable with a skill that runs local Node rendering tools and creates .md, .svg, and .png files. Use explicit safe output paths, avoid untrusted oversized SVG inputs, and expect the bundled templates to use Chinese sample content unless you ask the agent to generate in another language.
scripts/svg2png.js:148Unbounded SVG Processing Enables Resource-Exhaustion Denial of Service
Instruction-capable artifact exceeds whole-file semantic analysis limits
The skill explicitly instructs the agent to write generated SVG and PNG files to disk or a project directory without requiring user confirmation, a declared output path, or any safety constraints on where files may be written. In an agent context, implicit filesystem writes can cause unintended data modification, overwrite existing files, or leave sensitive/generated artifacts on disk, especially when titles or directories are influenced by user input.
Artifact content does not match its filename extension
This template hardcodes all user-facing content in Chinese, including the title, description, labels, and annotations. That creates a language/locale constraint without offering an explicit user choice, which matches the policy category for forced language behavior.
The template’s visible title, labels, and descriptions are entirely in Chinese, which implies the skill is constrained to a specific language. There is no indication that the user can choose another language or that the template is intentionally limited to a Chinese-only regional context.
The template’s user-facing title, labels, and descriptions are entirely in Chinese, which implies the skill output is constrained to a specific language. There is no accompanying instruction or note indicating that Chinese is optional, user-selected, or required for a justified region-specific use case.
This file’s natural-language content, including the title and all labels/descriptions, is fixed to a single language. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale constraint is clearly documented and justified, which is not present here.
This markdown template hard-codes all user-facing content in Chinese, including the title and comparison labels, with no indication that the skill is China-specific or that users can opt into another language. That creates a natural-language policy concern because it forces a specific language by default.
This markdown file contains all user-facing content in Chinese, including the title and descriptions, with no indication that the skill is region-specific or that users can opt into this language. That creates a natural-language policy concern because the skill effectively forces a specific language without documented justification or choice.
This file’s natural-language content is entirely Chinese, including the title, labels, and descriptions, but there is no indication that the skill is region-specific or that users can opt into this locale. Under the policy, forcing a specific language without user choice is a natural-language policy violation.
The natural-language content in the template is entirely in Chinese, including the title, labels, and descriptions, with no indication that language selection is optional or region-specific. This can violate language/locale policy because it implicitly constrains generated output to a specific language without user opt-in.
The template’s user-facing title, labels, and descriptions are entirely in Chinese, which encodes a specific language choice in the skill content. For this file, there is no indication that the locale is optional, user-selected, or justified as a region-specific template, so it constitutes a language/locale policy concern.
The natural-language content in the template is entirely in Chinese, including the title and descriptive labels, with no indication that language selection is optional or that the skill is intended only for a Chinese-speaking locale. This can violate language/locale policy when a skill implicitly forces a specific language without user opt-in.
The user-facing title and descriptions are entirely in Chinese, and the template provides no indication that language selection is optional or that the skill is intended only for a Chinese-language context. This creates a natural-language policy concern because the skill effectively enforces a specific locale without user opt-in.
The template’s natural-language content is entirely in Chinese, including the title, labels, and descriptions, with no indication that the skill supports user language choice or that it is intentionally limited to a Chinese-only context. This can violate language/locale policy when a skill implicitly forces a specific language without opt-in.
The template hard-codes all visible content in Chinese, which can override or constrain the user's expected language and reduce transparency for non-Chinese speakers. While this is not a code-execution or data-exfiltration issue, it is a real policy and usability vulnerability because it can cause misleading output, limit accessibility, and create inconsistent behavior when the user did not request Chinese output.
The file’s user-facing content is entirely in Chinese (for example, the title and all quadrant labels/descriptions), with no indication that the language is configurable or intended only for a Chinese-speaking context. This can violate language/locale policy when a skill implicitly forces one language without offering user choice or documenting a justified locale constraint.
The template hard-codes all user-visible content in Chinese, which can override or ignore the user's language preference and produce output the user did not request. In an infographic-generation skill, this is primarily a safety and quality problem rather than a direct exploit, but it can mislead users, reduce accessibility, and cause policy noncompliance where user choice or localization is expected.
This template is entirely authored with Chinese title, description, and labels, which indicates a fixed language/locale choice embedded in the skill content. Under the policy, forcing a specific language without user opt-in or clear justification is a natural-language policy concern.
The file's user-facing content is entirely in Chinese, including the title, description, and all labels, with no indication that the skill offers a language choice or is explicitly limited to a Chinese-speaking context. Under the language/locale policy, forcing a specific language without user opt-in can be a natural-language policy violation.
The skill content is entirely written in Chinese, including the title, description, and all labels, with no indication that the user can choose another language or that the skill is intentionally limited to a Chinese-speaking context. This is a natural-language locale constraint that may violate organizational language/locale policy when presented without opt-in or justification.
The natural-language content of the skill is entirely in Chinese, and there is no indication that the user can choose another language or that the locale restriction is intentional for a region-specific use case. Under the policy, language constraints should be opt-in or clearly justified.
The skill template content is entirely in Chinese, including the title, description, and all labels, with no indication that the language is optional or tied to a justified region-specific use case. This can violate language/locale policy when users are not given a choice or opt-in for the forced locale.
The template hard-codes Chinese labels and descriptions throughout the skill content, such as the title, description, and node labels. This imposes a specific language on outputs without any visible user opt-in or justification that the skill is intended only for a Chinese-language or region-specific context.
The file’s user-facing content is entirely written in Chinese, with no indication that language selection is optional or that the skill is intended only for a Chinese-language context. Per the policy, forcing a specific language without user opt-in can be a natural-language policy violation.