T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned Third-Party Python Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 4
Vulnerability Type: Unpinned third-party dependencies and non-reproducible installation
Risk Level: MediumVulnerable Code
yaml metadata: {"openclaw":{"emoji":"🔎","requires":{"bins":["python"]},"install":[{"id":"pip","kind":"uv","packages":["fastapi","uvicorn","pydantic"]}]}}Technical Analysis
The installation metadata requests
fastapi,uvicorn, andpydanticwithout exact version constraints or cryptographic hashes. Consequently, installations performed at different times can resolve to different package versions.This is a supply-chain weakness because the effective code installed with the Skill is not fully defined by the reviewed project. If a future dependency release is compromised, malicious, or incompatible, the package manager may resolve and install it automatically. Dependency code can execute during installation, import, application startup, or request processing.
The audit found no evidence that the named packages are currently malicious. The risk arises from mutable and unverified dependency resolution.
Attack Path
- An attacker compromises a listed package, its maintainer account, release infrastructure, or another dependency in its transitive dependency graph.
- The attacker publishes a malicious version that remains eligible because the Skill specifies no version constraints.
- A user installs the Skill using the declared
uvinstallation procedure. - The package manager resolves the compromised release and installs it.
- Malicious code executes during package installation, module import, Uvicorn startup, or API operation under the privileges of the user running the Skill.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the privileges of the account installing or running the Skill. Depending on that account's permissions and environment, the compromised dependency could access application data ...[truncated 314 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin every direct dependency to an exact, reviewed version, for example:
yaml "packages":["fastapi==<reviewed-version>","uvicorn==<reviewed-version>","pydantic==<reviewed-version>"] -
Generate and commit a lockfile that records the complete transitive dependency graph.
-
Require cryptographic hashes for downloaded distributions where supported.
-
Install only from an explicitly configured trusted package index over TLS.
-
Run automated vulnerability and provenance checks against both direct and transitive dependencies.
-
Review and deliberately update dependency pins instead of resolving unrestricted latest versions during installation.
-
Run installation and the API server as a dedicated, non-privileged account in an isolated environment with restricted filesystem and network access.
-
