finding-tests
Pass
Audited by Gen Agent Trust Hub on Sep 22, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONCOMMAND_EXECUTION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill is vulnerable to command injection because it interpolates untrusted user data (class names, namespaces, and file paths) directly into a shell command executed via
execute_tool. While the documentation advises wrapping values with spaces in single quotes, it fails to provide guidelines for sanitizing or escaping shell-active metacharacters such as semicolons (;), pipes (|), ampersands (&), or backticks (`). An attacker could provide a crafted input that breaks out of the intended command to execute arbitrary shell operations. - Ingestion points: User-supplied strings for
--className,--classNamespace,--filePath,--methodName, and--methodArgumentsinSKILL.md. - Boundary markers: The instructions recommend using single quotes for parameters containing spaces.
- Capability inventory: The
execute_toolfunction is used to invoke a system-level CLI tool (findTests). - Sanitization: There is no evidence of input validation, sanitization, or escaping for shell metacharacters beyond simple space-quoting.
- [COMMAND_EXECUTION]: The skill's primary function is the execution of a system command (
findTests) through theexecute_toolcapability. While this is the intended design for a JetBrains development tool, the combination of CLI execution and the aforementioned lack of input sanitization constitutes a security risk.
Audit Metadata