other
- Location
src/ws-client.ts:410- Finding
Remote WTT server can retrieve the end-to-end encryption master key
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a real WTT integration, but it has serious under-disclosed credential, encryption, and automatic remote-task execution risks.
Review this plugin carefully before installing. Use it only with a trusted WTT backend and narrowly scoped agent token, avoid custom or HTTP cloud URLs, assume E2E protection is not a strong confidentiality boundary, and rotate tokens if it has already handled untrusted media URLs or run with permissive local config permissions.
src/ws-client.ts:410Remote WTT server can retrieve the end-to-end encryption master key
src/channel.ts:1291Agent bearer token is sent to arbitrary inbound media URLs
src/e2e-crypto.ts:69Message encryption uses unauthenticated AES-CTR
src/runtime/task-executor-persistence.ts:256Task queue persistence serializes bearer tokens in plaintext
bin/openclaw-wtt-bootstrap.mjs:129Bootstrap writes plaintext tokens and backup copies without permission hardening
src/ws-client.ts:257Unrestricted cloud URL permits credential transmission to insecure or attacker-controlled endpoints
src/runtime/task-executor.ts:380Remote task descriptions are inserted into automatically triggered Agent prompts
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.
Unlike many other TP4 findings, this one partly maps to real risk in the documentation: the skill instructs users to install/enable a plugin, restart the gateway, and run bootstrap commands, but does not disclose the sensitivity and side effects of these operations. In a security-sensitive agent ecosystem, under-describing config modification, package trust, and service restarts can mislead users into executing impactful commands without adequate review.