T03 · Remote Payload Retrieval and Execution
Warning
- Location
scripts/env_init.sh:28- Finding
Unverified Remote SDK Retrieval and Execution
- Content
View full analysis
/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' || echo "0.0.0") remote_ver=$(echo "$manifest" | jq -r '.sdk_version // "unknown"') if [ "$local_ver" = "0.0.0" ] || [ "$local_ver" != "$remote_ver" ]; then echo "📦 SDK 更新: $local_ver → $remote_ver，正在安装..." pip install --quiet --upgrade https://las-ai-cn-beijing-online.tos-cn-beijing.volces.com/operator_cards_serving/public/skills/sdk/las_sdk-0.2.0-py3-none-any.whl fi ``` ### Technical Analysis The mandatory environment-initialization procedure retrieves a remote manifest and automatically installs a Python wheel from an external URL. Neither the manifest nor the wheel is authenticated using a pinned cryptographic hash or trusted package signature. HTTPS provides transport security but does not protect against compromise of the hosting account, object-storage configuration, publication pipeline, or another trusted component. The effective package payload can therefore change after the skill has been reviewed without any corresponding modification to this repository. A malicious wheel can install executable modules, replace the `lasutil` entry point, or include Python startup behavior such as a malicious `.pth` file. The installed code may consequently run when Python or `lasutil` is subsequently invoked. The manifest also controls whether the installation branch executes, while the downloaded wheel URL is independently hard-coded. This creates an inconsistent update mechanism in which any reported remote version differing from ...[truncated 1546 chars]- Remediation
View remediation