T08 · Insecure Dependencies
- Location
scripts/install_chromedriver.sh:63- Finding
Third-Party Dependencies and ChromeDriver Are Installed Without Integrity Verification
- Content
View full analysis
=4.15.0; python_version >= '3.7' selenium>=3.141.0,<4.0.0; python_version < '3.7' # Optional (publish fallback on VNC): pip3 install pyautogui ``` ```bash ZIP_URL="https://storage.googleapis.com/chrome-for-testing-public/${FULL_VERSION}/linux64/chromedriver-linux64.zip" TMPDIR=$(mktemp -d) trap 'rm -rf "$TMPDIR"' EXIT echo "Downloading: $ZIP_URL" if ! curl -fL "$ZIP_URL" -o "$TMPDIR/chromedriver.zip"; then echo "Download failed for version $FULL_VERSION." >&2 exit 1 fi unzip -o -q "$TMPDIR/chromedriver.zip" -d "$TMPDIR" DEST="$INSTALL_DIR/chromedriver" cp -f "$TMPDIR/chromedriver-linux64/chromedriver" "$DEST" chmod 755 "$DEST" ``` ### Technical Analysis The setup process installs Selenium from the active Python package index using broad version ranges and without cryptographic hashes. Consequently, the precise code installed can change over time without any modification to the reviewed Skill. The documentation also recommends installing `pyautogui` without a pinned version or hash. ChromeDriver is retrieved from Google's official HTTPS storage, but the downloaded archive is neither checksum-verified nor signature-verified before its executable is installed and subsequently launched. HTTPS protects transport under normal circumstances but does not provide an independent artifact-integrity guarantee against a compromised package release, package index, repository, certificate trust chain, or upstream account. ### Attack Path 1. An attacker compromises an applicable package release, package index, upstream account, download repository, or tra ...[truncated 1090 chars]- Remediation
View remediation
