openocd
Pass
Audited by Gen Agent Trust Hub on Apr 19, 2026
Risk Level: SAFECOMMAND_EXECUTION
Full Analysis
- [COMMAND_EXECUTION]: The skill uses the Python
subprocessmodule to executeopenocdandarm-none-eabi-gdbcommands. - Evidence: Found in
scripts/openocd_run.py,scripts/openocd_gdb.py, andscripts/openocd_telnet.py. The scripts construct command-line arguments to perform chip flashing, memory erasing, and debugging. - Context: This behavior is intended and required for the skill's purpose. Paths to the executables are configurable in the environment via
config.json. - [DATA_EXFILTRATION]: Analysis of network operations shows communication is limited to local debugger ports.
- Evidence:
scripts/openocd_telnet.pyandscripts/openocd_itm.pyconnect tolocalhost(127.0.0.1) on ports 3333, 4444, and 3443. - Context: No data is transmitted to external or untrusted domains.
- [INDIRECT_PROMPT_INJECTION]: The skill processes output from external hardware targets, presenting a theoretical surface for indirect injection.
- Ingestion points: Target output is captured via Semihosting in
scripts/openocd_semihosting.pyand ITM inscripts/openocd_itm.py. - Boundary markers: None present. The output is returned within structured JSON fields to the agent.
- Capability inventory: The agent has the ability to flash firmware, write to memory, and reset targets using the skill's scripts.
- Sanitization: No sanitization of target output is performed.
- Context: While this represents a technical attack surface, it is a standard characteristic of hardware debugging tools and is generally acceptable given the local environment.
Audit Metadata