T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unpinned Third-Party Package Retrieval and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21–23
Vulnerability Type: Unpinned dependency dynamically retrieved and executed throughuvx
Risk Level: Mediumsh uvx --from yunohost-mcp-connect yunohost-mcp-connect setup \ --server https://your-yunohost-domain/mcp \ --client openclawTechnical Analysis
The skill directs the agent to retrieve and immediately execute the third-party
yunohost-mcp-connectpackage without specifying an audited version, immutable artifact, or integrity hash. Consequently, the code executed by this command can change after the skill has been reviewed.The package runs with the invoking user's privileges. According to the surrounding instructions, it is expected to generate Nostr identity material and modify
~/.openclaw/openclaw.jsonor the file selected throughOPENCLAW_CONFIG_PATH. This gives the dynamically retrieved package access to sensitive authentication material and local configuration.Attack Path
- An attacker compromises the package registry entry, maintainer account, build pipeline, or a subsequently published package release.
- The user or agent follows the skill and invokes the documented
uvxcommand. uvxretrieves the currently available package rather than a fixed, previously audited artifact.- The compromised package executes locally with the user's permissions.
- Malicious package code can read accessible files, capture generated identity material, alter OpenClaw configuration, or execute other commands within the user's privilege boundary.
Impact Assessment
Successful exploitation permits arbitrary code execution with the privileges of the user running the setup. The affected scope includes files readable or writable by that user, OpenClaw configuration, generated Nostr credentials, environment variables, and accessible network resources.
The command does not explicitly request elevated privileges, so sy ...[truncated 195 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
yunohost-mcp-connectto a specifically reviewed version rather than resolving the latest available release. - Use an immutable, trusted artifact and verify its cryptographic hash before execution.
- Maintain a lock file or controlled package manifest containing exact versions and integrity metadata.
- Document the approved package registry and reject alternative or untrusted indexes.
- Review the selected package release and its transitive dependencies before updating the pinned version.
- Back up the OpenClaw configuration before setup and verify that unrelated settings remain unchanged afterward.
- Ensure generated private-key files and configuration files have user-only permissions.
- Where feasible, execute initial setup in a restricted environment with only the filesystem and network access required for configuration.
- Pin
