T08 · Insecure Dependencies
- Location
install.sh:8- Finding
Unpinned Third-Party SDK Installation from a Mutable Package Registry
- Content
View full analysis
Vulnerability Details
File Location:
install.sh:8-15
Vulnerability Type: Unpinned dependency installation and unsafe modification of a system-managed Python environment
Risk Level: MediumVulnerable Code
sh if command -v pip3 >/dev/null 2>&1; then pip3 install --upgrade ceki-sdk --break-system-packages 2>/dev/null \ || pip3 install --upgrade --user ceki-sdk elif command -v pip >/dev/null 2>&1; then pip install --upgrade ceki-sdk --break-system-packages 2>/dev/null \ || pip install --upgrade --user ceki-sdk else echo "❌ pip not found. Install Python 3.10+ first." exit 1 fiRelated unpinned installation instructions also appear in:
SKILL.md:56-60README.md:33-37examples/python-quickstart.py:7-9examples/node-quickstart.ts:6-8
The manifest only specifies a lower bound rather than a reviewed release:
json "dependencies": { "ceki-sdk": ">=2.18.0" }Technical Analysis
The installation script uses
pip install --upgradewithout an exact version, lockfile, or package hash. Consequently, the code installed and executed is determined by the package registry at installation time rather than by the audited project contents. A future release ofceki-sdk, one of its transitive dependencies, or a compromised publisher account could therefore change the effective behavior after this skill has been reviewed.Python package installation can execute package build hooks and install executable entry points. The installed
cekiclient subsequently receives theCEKI_API_KEY, controls remote browser sessions, processes screenshots and chat messages, and reads or writes session state. A malicious package version would run locally with the privileges of the user invoking the installer and could access data available to that account.The initial installation attempt also uses
--break-system-packages. This bypasses ...[truncated 2509 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the SDK to an exact, reviewed version, for example:
sh python3 -m pip install "ceki-sdk==2.18.0" - Require package integrity verification using
--require-hashesand a checked-in requirements file containing hashes for the SDK and all transitive dependencies:sh python3 -m pip install --require-hashes -r requirements.lock - Remove
--break-system-packages. Create an isolated virtual environment or usepipxinstead:sh python3 -m venv "$HOME/.local/share/realbrowser/venv" "$HOME/.local/share/realbrowser/venv/bin/python" -m pip install \ --require-hashes -r requirements.lock - Replace
"ceki-sdk": ">=2.18.0"inmanifest.jsonwith an exact reviewed version and update it only through a controlled dependency-review process. - Pin the Node.js package to an exact version and provide a committed lockfile with integrity metadata.
- Avoid automatic upgrades during normal installation. Publish version updates as explicit, reviewed skill releases.
- Verify package provenance through signed releases or registry attestations where available, and document the expected publisher and package hashes.
- Run dependency scanning and software-composition analysis before approving each updated SDK or lockfile.
- Pin the SDK to an exact, reviewed version, for example:
