T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:5
- Finding
- Unpinned Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, line 5 **Vulnerability Type**: Unpinned dependency and insufficient package integrity verification **Risk Level**: Medium ### Vulnerable Code ```yaml metadata: {"clawdbot":{"emoji":"📺","requires":{"bins":["catt"]},"install":[{"id":"pip","kind":"uv","package":"catt","bins":["catt"],"label":"Install via pip/uv"}]}} ``` ### Technical Analysis The skill metadata directs the installer to retrieve the third-party `catt` package without specifying an exact version or cryptographic integrity hash. Dependency resolution can therefore select package contents that differ from those reviewed during this audit. Transitive dependencies are also not locked or verified. The package name is consistent with the skill's declared purpose and homepage, and there is no evidence in the reviewed file that the current package is malicious. Nevertheless, relying on an unpinned package from an external registry creates a supply-chain exposure: compromise of the package publisher, package registry, or a transitive dependency could cause attacker-controlled code to be installed or executed. ### Attack Path 1. An attacker compromises the upstream `catt` distribution channel, publisher account, or one of its unconstrained transitive dependencies. 2. The attacker publishes a modified package version containing malicious installation-time or runtime behavior. 3. A user installs the skill, and the `uv`/Python package resolver retrieves the current unpinned package and dependencies. 4. Malicious code executes during package installation, import, or subsequent invocation of the `catt` binary. 5. The payload operates with the privileges of the account performing the installation or running the command. ### Impact Assessment Successful exploitation could permit arbitrary code execution under the installing or invoking user's account. The resulting access could include reading or modifying files ava ...[truncated 290 chars]
- Remediation
- ## Remediation Suggestions - Pin `catt` to an exact, reviewed release rather than resolving the latest available version. - Record and verify cryptographic hashes for the package artifacts. - Lock all transitive dependencies using a reproducible lockfile or equivalent constraints. - Retrieve packages only from a trusted, explicitly configured package index. - Perform installation in an isolated, least-privileged environment. - Regularly review pinned dependencies for security advisories and update them through a controlled review process. - Where supported by the skill packaging system, verify package provenance or signed release artifacts before installation.