T05 · Unauthorized Access and Privilege Escalation
- Location
index.js:273- Finding
Arbitrary Local File Disclosure Through Unrestricted Absolute Paths
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a real Feishu file-sending tool, but it can upload local files with broad chat triggers and too little confirmation or path restriction.
Review this before installing in any shared or production OpenClaw environment. Only use it where chat participants are trusted, Feishu recipients are verified, and the process has access only to files that are safe to send. The publisher should restrict sends to an approved directory, require confirmation showing path, size, and recipient, remove contains triggers, enforce file size/type checks, and replace 777 log permissions with owner-only permissions.
index.js:273Arbitrary Local File Disclosure Through Unrestricted Absolute Paths
index.js:143Denial of Service Through Unbounded Synchronous File Loading
index.js:68World-Writable Log Directory and Unsafe Permission Guidance
The skill is presented as a simple file-sending utility, but the documentation reveals materially broader capabilities: recursive local file search, reading arbitrary user-specified paths, creating logs/config files, and making outbound API calls. That mismatch weakens informed consent and makes it easier for a user or calling agent to trigger sensitive file discovery and exfiltration behavior without clearly understanding the scope.
The documented trigger phrases include broad natural-language patterns such as common requests to 'send' or '发一下', which overlap with ordinary conversation. In a chat-integrated skill that can search local files and send them externally, unintended activation materially increases the risk of accidental file disclosure.
The trigger rule set uses ambiguous prefix_match and especially contains rules for phrases like '发文件' and '发送文件', making activation possible from incidental text. Given the skill can recursively search the workspace and transmit files, this broad matching meaningfully raises the chance of unintended execution and data exfiltration.
Recommending chmod -R 777 logs instructs users to make the log directory world-readable and world-writable. If logs contain filenames, recipient identifiers, tokens, errors, or other operational details, this can enable local tampering, unauthorized reading, or destruction of forensic evidence by other users/processes on the system.
|------|----------|
| **文件发错地方(发到个人而不是群里)** | 机器人触发时自动识别;命令行调用必须加 `--to "chat:群聊 ID"` |
| 文件名异常 | 使用最终版 index.js |
| 无日志 | 赋权 logs 目录:`chmod -R 777 logs` |
| 机器人无响应 | 重启 OpenClaw,检查文件路径 |
| 发送失败 | 检查飞书权限与 appId/appSecret 配置 |
| token 获取失败 | 检查 appId/appSecret 是否正确 |
The prefix triggers like '帮我发', '发一下', and '把文件' are so generic that the skill can activate during ordinary conversation rather than an explicit file-send request. In a messaging/file-transfer skill, accidental activation is dangerous because it may cause unintended file delivery, recipient auto-selection, or leakage of sensitive local files through natural-language ambiguity.
Contains-match triggers for common phrases like '发文件' and '发送文件' can fire when those words appear anywhere in a message, including discussion about sending files rather than a request to do so. Because this skill performs outbound file transmission, unintended activation can directly lead to privacy breaches, misdelivery, or unauthorized actions with minimal user awareness.
The README explicitly promotes sending arbitrary local files to Feishu, but it does not clearly warn users that file contents will leave the local machine and be transmitted to an external service. In an agent/automation context, this increases the risk of unintended exfiltration of sensitive documents, keys, or internal data if users or upstream prompts provide broad paths or ambiguous search terms.
The documentation says the recipient parameter is required, but also states the tool will default to sending to a personal recipient if it is omitted. This inconsistency can cause accidental delivery of sensitive files to the wrong destination, especially in CLI or automated contexts where operators assume omission will fail safely.
The skill silently creates a recipient configuration file in the user's home workspace based on global configuration, without explicit consent. Unexpected persistence of messaging targets can alter future behavior, leak recipient metadata to disk, and make later file transmission happen to an unintended default target.
In robot mode, the skill extracts file paths or searches the workspace from free-form user input and then uploads matching local files to Feishu. Because it does not clearly warn that local file contents will be transmitted externally or require an explicit confirmation step, users can unintentionally exfiltrate sensitive local data, especially in chat-driven workflows where intent may be ambiguous.
The batch-selection flow supports sending multiple matched files or all matches with a simple reply, but it provides no explicit safety warning about transmitting those files to an external service. This amplifies the risk of accidental bulk exfiltration from the workspace, particularly because matching is based on broad search results and the user may not inspect every selected file carefully.
The natural-language description is written as a Chinese-only interaction model and states support for commands and natural language without indicating that users may choose another language. Under the policy, language constraints should be optional or explicitly justified when the skill enforces a locale.
The note text is written only in Chinese ("示例配置 - 请替换为你的用户 Open ID"), which imposes a specific language in a user-facing configuration comment. The file does not provide an alternative language, opt-in, or any indication that the skill is intentionally region-specific.
The stated purpose is a Feishu bulk file sending skill, but this function additionally reads from and auto-writes recipient configuration under the user's home directory. Persisting local recipient defaults is a convenience feature rather than an obvious requirement of file delivery itself, so it adds capability beyond the manifest's narrow stated purpose.
The manifest describes a file sending skill, but the code also creates a logs directory and continuously appends operational data to disk. Local logging is not an obvious user-facing requirement of bulk file sending, especially when the description emphasizes simplicity and zero dependency rather than filesystem side effects.
This manifest only provides a brief description of the skill as a Feishu bulk file sending skill, but does not specify how or when it should be invoked. For manifest files, missing specificity around trigger scope or constraints can lead to unintended or overly broad activation behavior.