T08 · Insecure Dependencies
- Location
SKILL.md:6- Finding
Unpinned and Unnecessary Third-Party Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 6
Vulnerability Type: Supply-chain exposure through unpinned dependencies
Risk Level: MediumVulnerable Code
yaml metadata: { "openclaw": { "emoji": "📊", "requires": {"pip": ["baostock", "akshare", "pandas"]} } }Technical Analysis
The skill declares
baostock,akshare, andpandaswithout exact versions or package integrity hashes. Consequently, installation may resolve different package releases over time rather than a fixed, previously reviewed dependency set.If a declared package, one of its transitive dependencies, or its release infrastructure is compromised, a future installation could retrieve attacker-controlled package content. Python packages may execute code during installation or when imported. The current implementation imports
akshareandpandas;baostockis declared but not used, while the importedpandasmodule is also unused in the reviewed implementation. These unnecessary declarations increase the supply-chain attack surface without supporting current functionality.The audit found no evidence that the named packages are presently malicious. The finding concerns the absence of version and integrity controls.
Attack Path
- An attacker compromises a declared package, a transitive dependency, or the associated package publishing account.
- The attacker publishes a malicious release under the legitimate package name.
- A new skill environment processes the unpinned
piprequirements and resolves the malicious release. - Attacker-controlled code runs during package installation or when the skill imports the affected module.
- The payload operates with the permissions of the process installing or executing the skill.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the skill runner's operating-system account. The resul ...[truncated 409 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
baostockandpandasfrom the declared requirements unless they are required by supported functionality. - Pin every direct dependency to an exact, reviewed version rather than allowing unconstrained resolution.
- Generate and maintain a lockfile that also fixes transitive dependency versions.
- Require package hashes during installation, such as through a hash-locked requirements file and
pip install --require-hashes. - Retrieve packages only from an approved repository and disable untrusted supplemental indexes to reduce dependency-confusion risk.
- Scan pinned packages for known vulnerabilities and review dependency updates before changing the lockfile.
- Install and execute the skill in a least-privileged, isolated environment without unnecessary credentials or filesystem access.
- Remove
