Remote control for aria2 download service via JSON-RPC 2.0. Supports adding downloads (HTTP/FTP/Torrent/Magnet), querying task status, pausing/resuming, and...

This skill appears to be a straightforward aria2 JSON-RPC client and is internally consistent. Before installing, check these small issues: (1) the metadata lists curl as a required binary even though the Python client uses requests — curl is not necessary; (2) the docs show running aria2c to enable RPC but aria2c is not declared as a required binary — if you plan to control a local aria2 instance you must have aria2/aria2c available; (3) be careful which RPC URL and secret you supply — the script will send commands (and in the case of add-torrent/add-metalink will read local files you point it at and encode/send them) to whatever RPC endpoint is configured; ensure that endpoint is trusted; (4) review scripts/aria2_rpc.py yourself if you need higher assurance. If you only intend to control a local aria2 instance, use defaults and keep ARIA2_RPC_SECRET private.

Type: OpenClaw Skill Name: aria2-rpc Version: 0.1.2 The skill is designed to remotely control an aria2 download service via JSON-RPC, which inherently involves network and file system interactions. While its core functionality is legitimate, the `scripts/aria2_rpc.py` script exposes several capabilities that could be abused if an attacker can control the inputs (e.g., via prompt injection against the OpenClaw agent). These include: 1) Local File Read (LFR) vulnerability: The `add_torrent` and `add_metalink` methods read local files (e.g., `torrent_path`) and send their base64-encoded content to the aria2 RPC server. An attacker could potentially trick the agent into providing a path to a sensitive file, leading to its exfiltration to the aria2 server. 2) Local File Write (LFW) / Configuration Manipulation vulnerability: The `add-uri` command allows specifying `--dir` and `--out` options, and `set-global-option`/`set-option` allow setting arbitrary aria2 configuration keys (e.g., `dir`, `save-session`, `user-agent`, `all-proxy`). This could be exploited to write files to arbitrary locations on the aria2 server's filesystem or manipulate its behavior. 3) Arbitrary Network Requests: The `rpc-url` can be controlled by environment variables or command-line arguments, allowing the script to make requests to arbitrary internal or external endpoints. The `SKILL.md` also grants broad `Bash(aria2:*)` permissions, further increasing the attack surface. These are significant vulnerabilities, but the code does not show clear evidence of intentional malicious behavior (e.g., exfiltrating data to an unauthorized third party, installing backdoors).