T08 · Insecure Dependencies
- Location
scripts/publish.sh:13- Finding
Unpinned Runtime Installation of Playwright and Chromium
- Content
View full analysis
/dev/null; then echo "Installing Playwright..." pip3 install playwright playwright install chromium fi ``` ### Technical Analysis The launcher installs the latest available Playwright package and downloads Chromium during normal execution. Neither component is pinned to a reviewed version or validated with cryptographic hashes. There is also no lockfile, isolated virtual environment, or trusted package-index enforcement. Consequently, the code executed by this Skill can change without any corresponding change to the reviewed project. The installation also relies on the user's current `pip3` and Playwright configuration, including any configured package mirrors, proxies, or environment variables. ### Attack Path 1. A user runs `scripts/publish.sh` on a system where the `playwright` Python module is unavailable. 2. The script invokes `pip3 install playwright` against the currently configured package source. 3. It then invokes `playwright install chromium`, causing additional browser artifacts to be downloaded. 4. If the package source, configured mirror, dependency release, downloaded browser artifact, or network path is compromised, attacker-controlled installation or package code may execute. 5. That code executes with the privileges of the user who launched the Skill. ### Impact Assessment Successful supply-chain exploitation could provide arbitrary local code execution with the invoking user's privileges. This may expose files, browser data, environment variables, and account information accessible to that user. The script does not itself request privilege elevation, so the direct scope is limited to the launcher's existing permissions. ]]>- Remediation
View remediation
