T08 · Insecure Dependencies
- Location
SKILL.md:97- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 97
Vulnerability Type: Unpinned third-party dependencies
Risk Level: MediumVulnerable Code
bash pip install pyrealsense2 opencv-python numpyTechnical Analysis
The installation command retrieves mutable package versions from pip's configured package index without version constraints, cryptographic hashes, a lockfile, or an explicitly trusted package source. Consequently, the code ultimately installed and imported can change after this Skill has been reviewed.
The listed package names do not appear to be typosquatted, and the project does not specify a suspicious custom package repository. This finding therefore represents an avoidable supply-chain exposure rather than evidence that the current dependencies are malicious.
Exploitation would require compromise or substitution of a named package, one of its transitive dependencies, or the package index or pip configuration used by the victim.
Attack Path
- A user follows the dependency installation instruction in
SKILL.md. - pip resolves the latest packages available through its configured index.
- An attacker-controlled or compromised release is selected because no approved versions or hashes are enforced.
- Malicious package code executes during installation or when imported by the collection scripts.
- The code runs with the privileges of the user who installed or launched the Skill.
Impact Assessment
Successful exploitation could execute arbitrary code with the invoking user's privileges. Its scope could include access to local files available to that user, environment variables, the Agent workspace, connected camera data, and captured RGB-D datasets. It would not inherently grant administrator privileges unless installation or execution were performed from an elevated account.
- A user follows the dependency installation instruction in
- Remediation
View remediation
Remediation Suggestions
-
Move dependencies into a reviewed and version-controlled requirements file.
-
Pin every direct and transitive dependency to an approved exact version.
-
Record cryptographic hashes and enforce them during installation:
bash python -m pip install --require-hashes -r requirements.txt -
Generate the locked dependency set in a controlled environment using a tool such as
pip-tools. -
Use an explicitly trusted package index or an internally controlled package mirror.
-
Scan locked dependencies for known vulnerabilities and review updates before changing pins.
-
Install and run the Skill in a least-privileged virtual environment rather than an elevated system environment.
-
