omada-controller
Fail
Audited by Gen Agent Trust Hub on Oct 24, 2026
Risk Level: HIGHCREDENTIALS_UNSAFECOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTIONEXTERNAL_DOWNLOADS
Full Analysis
- [CREDENTIALS_UNSAFE]: The Python scripts
omada_api_client.pyanddeploy_omada_ssid.pycontain hardcoded credentials (PASSWORD = "SecurePassword123"andPASSWORD = "SecretPassword123"). Furthermore, both scripts explicitly disable SSL certificate verification (self.session.verify = Falseandurllib3.disable_warnings), which exposes session tokens and credentials to man-in-the-middle attacks. - [COMMAND_EXECUTION]: The skill provides numerous instructions for executing privileged shell commands using
sudo. This includes modifying system firewall rules (sudo ufw allow), managing system services (sudo systemctl restart), and deleting files in protected system directories (sudo rm -f /opt/tplink/EAPController/data/db/mongod.lock). - [INDIRECT_PROMPT_INJECTION]:
- Ingestion points: The skill retrieves and displays untrusted data from the Omada Controller API, including device names, model identifiers, client connection statistics, and rogue AP alerts.
- Boundary markers: The skill lacks boundary markers or instructions to treat data retrieved from the network controller as untrusted.
- Capability inventory: The agent is authorized to perform privileged command execution (
sudo), file system modifications, and network operations. - Sanitization: There is no evidence of sanitization or escaping of the metadata retrieved from the network controller before it is processed by the agent.
- [EXTERNAL_DOWNLOADS]: The
gpt.mdfile includes a Docker Compose configuration that pulls the third-party imagembentley/omada-controller:5.14from a public registry.
Recommendations
- AI detected serious security threats
Audit Metadata