T08 · Insecure Dependencies
- Location
SKILL.md:37- Finding
Unpinned Runtime Dependency Installation
- Content
View full analysis
/dev/null || pip3 install opencv-python-headless --quiet python3 -c "from PIL import Image" 2>/dev/null || pip3 install Pillow --quiet python3 -c "import numpy" 2>/dev/null || pip3 install numpy --quiet ``` ### Technical Analysis The skill directs the runtime to install `opencv-python-headless`, `Pillow`, and `numpy` without pinning reviewed versions or verifying package hashes. Consequently, the code installed during one invocation may differ from the code installed during a later invocation. Package installation can execute package build and installation logic. If the configured package index, dependency resolution process, package publisher account, or an upstream release is compromised, malicious code could execute during installation or when the installed module is imported. The commands also use whichever `pip3` executable and package index configuration are available in the environment, without validating either. This is a supply-chain weakness rather than evidence that the named packages are currently malicious. ### Attack Path 1. A required Python module is absent from the Agent environment. 2. The skill follows its dependency-check instructions and invokes `pip3 install`. 3. The package installer resolves the latest available compatible package from the configured index. 4. A compromised, substituted, or unexpectedly modified package is downloaded. 5. Package installation logic or subsequent module import executes attacker-controlled code with the privileges of the Agent process. ### Impact Assessment Successful exploitation could provide arbitrary code execution under the operating-system account running the Agent. The attacker could access files, environment variables, network resources, and credentials available t ...[truncated 180 chars]- Remediation
View remediation
