Back to skill

Security audit

Clawface

Security checks for vulnerabilities and agentic risk

Overview

The skill appears to run the advertised avatar chat UI, but the server it starts can use OpenClaw credentials with broad authority and is not sufficiently locked down.

Review before installing. Only run this on a trusted machine and private network, prefer loopback-only binding, use the least-privileged gateway token possible, and verify or pin the downloaded native TTS runtime before use. Stop the node process when finished.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Findings (3)

T05 · Unauthorized Access and Privilege Escalation

Error
Location
bin/serve.js:190
Finding

Unauthenticated WebSocket Proxy Grants Privileged Gateway Access

Content
View full analysis
{ brBuf = Buffer.concat([brBuf, chunk]); while (true) { const frame = decodeFrame(brBuf); if (!frame) break; brBuf = brBuf.subarray(frame.totalLen); if (frame.opcode === 0x08) { sendClose(gwSocket, true); gwSocket.end(); browserSocket.end(); return; } if (frame.opcode === 0x09) { sendPong(browserSocket, frame.payload, false); continue; } if (frame.opcode !== 0x01) continue; // Forward browser frames to gateway (must be masked per RFC 6455) sendText(gwSocket, frame.payload.toString("utf8"), true); ...[truncated 3432 chars]
Remediation
View remediation
{ console.log(`http://127.0.0.1:${port}`); }); ``` 2. Generate a cryptographically random, per-launch session token and require it during the WebSocket handshake. 3. Validate `Origin` against an explicit allowlist and reject missing or unexpected origins. 4. Validate `Host` and reject requests addressed through unapproved hostnames. 5. Do not provide a transparent arbitrary-message proxy. Parse browser messages and allowlist only the gateway methods needed by the avatar interface. 6. Request only the minimum gateway scopes necessary for chat functionality. Remove administrative, approval, and pairing scopes unless a documented feature strictly requires them. 7. Enforce message-size, connection-count, rate, and idle-time limits. 8. Return an error and close the connection if gateway credentials are incomplete or upstream authentication fails. 9. Consider using a narrowly scoped server-side API instead of exposing the gateway protocol directly to browser clients. ]]>

T09 · Insecure Skill Coding Practices

Warning
Location
bin/serve.js:363
Finding

Unauthenticated and Unbounded TTS Endpoint Enables Resource Exhaustion

Content
View full analysis
(body += chunk)); req.on("end", () => { let text; try { text = JSON.parse(body).text || ""; } catch { res.writeHead(400); res.end("Bad request"); return; } ``` ```js execFile( bin, [ `--vits-model=${modelFile}`, `--vits-tokens=${tokensFile}`, `--vits-data-dir=${dataDir}`, `--output-filename=${outputPath}`, text, ], { env, timeout: 30000 }, (err) => { if (err) { res.writeHead(500); res.end(`TTS failed: ${err.message}`); try { fs.rmSync(tmpDir, { recursive: true }); } catch {} return; } try { const audio = fs.readFileSync(outputPath); res.writeHead(200, { ...securityHeaders, "Content-Type": "audio/wav", "Content-Length": audio.length, }); res.end(audio); } finally { try { fs.rmSync(tmpDir, { recursive: true }); } catch {} } } ); ``` ```js if (urlPath === "/tts" && req.method === "POST") { return handleTts(req, res); } ``` ```js server.listen(port, () => { console.log(`http://localhost:${port}`); }); ``` ### Technical Analysis The `/tts` endpoint has no authentication or authorization check. Incoming request bodies are appended to a JavaScript string until the client finishes sending data, with no request-size or text-length limit. A sufficiently large request can consequently consume excessive process memory. Every valid request creates a temporary directory and launches the native `sherpa-onnx-offline-tts` executable. There is no concurrency cap, queue limit, or rate limit. Multiple simultaneous requests can therefore con ...[truncated 1527 chars]
Remediation
View remediation

T08 · Insecure Dependencies

Warning
Location
SKILL.md:13
Finding

Downloaded Native Runtime Is Not Protected by Integrity Verification

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Findings (15)

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

This finding reflects that the browser UI is not purely local display logic; it exchanges chat data with a backend via WebSocket and triggers TTS endpoints, which is materially broader than a simple static local page. Even if expected for a chat avatar, under-describing this behavior can mislead users about data flow and privacy exposure.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

This finding reflects that the browser UI is not purely local display logic; it exchanges chat data with a backend via WebSocket and triggers TTS endpoints, which is materially broader than a simple static local page. Even if expected for a chat avatar, under-describing this behavior can mislead users about data flow and privacy exposure.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
92% confidence
Finding

This finding reflects that the browser UI is not purely local display logic; it exchanges chat data with a backend via WebSocket and triggers TTS endpoints, which is materially broader than a simple static local page. Even if expected for a chat avatar, under-describing this behavior can mislead users about data flow and privacy exposure.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill is presented as a local web UI server, but it also upgrades browser WebSocket traffic and proxies it to a remote gateway while performing authenticated login using local device credentials and a gateway token. This expands the trust boundary substantially: any page that can reach the local port can potentially drive a privileged remote session through the user's machine, and the behavior is not clearly disclosed by the stated skill description.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding

The skill explicitly performs networked behavior: it downloads binaries/models during install and, at runtime, connects to an upstream gateway over WebSocket while serving a local HTTP interface. Declaring no permissions or allowed tool scope obscures these capabilities from reviewers and users, increasing the risk of unintended credential use and network access.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The description says only 'Start the Clawface 3D avatar web UI' without defining specific trigger phrases, scope constraints, or exclusion conditions. In a manifest/markdown file, this broad action-oriented wording can overlap with many generic requests involving avatars, chat UIs, or web interfaces, increasing the risk of unintended invocation.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The server reads device identity material from an identity file, derives a public key identifier, and later uses the private key for gateway authentication, but the user-facing behavior is not surfaced in the skill description or at runtime. Hidden handling of credentials increases the risk of users unknowingly exposing privileged identity material to a component they believe only serves static files.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The proxy constructs and sends authenticated connect frames containing a gateway token and device signature to a remote endpoint, yet this sensitive remote-auth behavior is not apparent from the skill's local-UI description. The mismatch in declared purpose makes the feature more dangerous because users may expose the service locally without realizing it brokers privileged remote access.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

In addition to serving static content, the skill exposes a POST /tts endpoint that accepts arbitrary text and invokes local speech synthesis tooling. Even though execFile avoids shell injection, this still exposes local code execution functionality over HTTP and can be abused by any local webpage or process that can access the listening port, potentially causing unwanted resource consumption or misuse of bundled tooling.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The code launches an external binary to process attacker-controlled text from an HTTP request. While the arguments are passed safely without a shell, this still creates an execution surface in a skill whose advertised purpose is only serving a local UI; if the TTS binary or model stack has parsing flaws, the endpoint becomes a reachable trigger for local exploitation or denial of service.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The bundled web UI does substantially more than the declared purpose of serving a local 3D avatar page: it establishes remote WebSocket chat, fetches chat history, sends chat prompts, invokes a /tts endpoint, and plays returned audio. This hidden capability expansion is dangerous because users and reviewers may grant trust or network access based on an incomplete manifest, enabling unexpected data flows and remote interaction.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The UI posts user-visible text to a /tts endpoint, receives audio data, decodes it, and plays it automatically. That is an additional networked/media-processing capability not implied by merely launching a local avatar UI, and it creates an undisclosed path for transmitting conversation content to a backend service.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The fetch('/tts', {body: JSON.stringify({text:a})}) request sends user text to a service without any visible consent or disclosure in this file. Because the skill is presented as a local avatar UI, this undisclosed transmission is more dangerous: users may reasonably assume their typed content stays local when it does not.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The code creates a WebSocket using a configurable wsUrl, sends chat.history and chat.send requests, and streams assistant responses, which is materially beyond 'start a local avatar web UI.' In this context, undisclosed remote communication increases risk of silent exfiltration of user prompts and server-driven content reaching the browser under the guise of a local-only tool.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The HTML root sets lang="en", which is a natural-language locale choice applied by default to the skill UI. Under the policy, forcing a specific language or locale without user opt-in can be a violation when no alternative or justification is provided.

Content

No source excerpt is available for this finding.