T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:42- Finding
Overly Broad Cross-Session Message Injection Permissions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill openly implements session callback and message injection, but it asks users to broaden session routing and optionally cross-agent routing in ways that need careful review before installation.
Install only if you deliberately need cron or external jobs to send results back into an existing OpenClaw/QClaw session. Prefer keeping visibility at tree when possible, avoid visibility=all and wildcard agent-to-agent rules, limit targets to explicit sessions, run gateway restarts only during a maintenance window, and restore the default routing setting after use.
SKILL.md:42Overly Broad Cross-Session Message Injection Permissions
SKILL.md:212Wildcard Cross-Agent Injection Configuration
SKILL.md:110Unsafe Force-Termination and Manual Gateway Restart Procedure
This section lays out a complete procedure for weakening session isolation (visibility=agent), restarting the gateway so the weaker policy takes effect, and then using that access to inject messages across sessions. That is dangerous because it normalizes privilege broadening and operationalizes cross-session command delivery, undermining isolation guarantees that would otherwise block unauthorized or unintended message routing.
The cron payload instructs an isolated session to send a crafted message into a target session while suppressing normal message/output behavior, which creates a covert indirect injection chain. This is dangerous because it enables hidden or hard-to-audit inter-session control flow where an external scheduler can trigger actions inside another conversation with its full context, potentially causing unauthorized task execution or confusing provenance.
The description says to use the skill when the user asks phrases like '定时任务完成后回到本对话继续推进' or '让任务结果上报到同一对话', but it does not clearly delimit whether this applies only to cron/OpenClaw session-injection workflows or to any request about continuing work in the same conversation. Without exclusions or negative examples, these trigger descriptions are broad enough to overlap with ordinary task-continuation requests.
The skill explicitly documents how to expand from same-session callbacks into cross-agent message injection by enabling broader visibility and agent-to-agent routing. This turns a narrowly scoped callback mechanism into a general lateral-messaging capability that can be abused to inject instructions into unrelated agents or sessions, increasing the blast radius well beyond the stated use case.
The top-level description emphasizes using cron, external processes, or another session to inject into a target session so the original conversation continues, especially when a task should report back to the same dialogue. L021-L024 extends this into general-purpose external triggering and monitoring/watchdog alerts that wake agents on anomalies, which goes beyond the narrower callback/session-resume framing in the manifest.