T08 · Insecure Dependencies
- Location
SKILL.md:38- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 38–42
Vulnerability Type: Unpinned runtime dependency installation
Risk Level: Mediummarkdown ## First run — install the one Python dependency The script uses [`httpx`](https://www.python-httpx.org/). If a command fails with `ModuleNotFoundError: No module named 'httpx'`, install it once: ```bash python3 -c "import httpx" || python3 -m pip install httpxtext ### Technical Analysis The documented fallback command installs `httpx` without a pinned version, lockfile, cryptographic hash verification, or explicit trusted package index. Consequently, the installed code may differ from the dependency that was present when the Skill was audited. Resolution also depends on the invoking environment's pip configuration, including custom or attacker-controlled indexes. Although `httpx` is a legitimate package and the project contains no evidence that it intentionally selects a malicious dependency, this installation pattern creates a supply-chain exposure. A compromised package release or package index could provide attacker-controlled code. That code would subsequently run during installation or when `scripts/amazon_api.py` imports `httpx`. ### Attack Path 1. The invoking environment does not already have the `httpx` module. 2. A user or Agent follows the first-run instruction in `SKILL.md`. 3. pip resolves the unpinned `httpx` dependency through its configured package indexes. 4. A compromised release or attacker-controlled index supplies a malicious distribution. 5. Malicious package code executes during installation or upon import by `scripts/amazon_api.py`. 6. Because the Skill requires Amazon LWA and AWS credentials in environment variables, the malicious dependency could read and exfiltrate those credentials or tamper with API traffic. ### Impact Assessment Successful exploitation would execute code with the privileges of the user running pip or the Skill. Potential scope includes ...[truncated 674 chars]- Remediation
View remediation
Remediation Suggestions
-
Add a reviewed dependency manifest that pins
httpxand all transitive dependencies to exact versions. -
Generate and verify cryptographic hashes for every permitted distribution.
-
Install dependencies using hash enforcement, for example:
bash python3 -m pip install --require-hashes -r requirements.txt -
Configure pip to use an explicitly trusted HTTPS package index rather than relying on ambient user configuration.
-
Install dependencies inside a dedicated virtual environment with minimal privileges.
-
Use automated dependency monitoring and deliberately update pins after security review and testing.
-
Avoid directing an Agent to perform mutable runtime installation automatically. Prefer preparing and verifying dependencies during a controlled packaging or deployment stage.
-