T08 · Insecure Dependencies
- Location
INTEGRATION_TEST.md:112- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
INTEGRATION_TEST.md, lines 112-119
Vulnerability Type: Unpinned dependency installation from the active Python package index
Risk Level: MediumVulnerable Code
bash # Check the requests library python3 -c "import requests; print('OK')" # Test network connectivity curl -I https://dongniao.net/taxonomy.html # Install requests (if needed) python3 -m pip install requestsTechnical Analysis
The troubleshooting guide instructs users to install the
requestspackage without specifying a reviewed version, verifying cryptographic hashes, using a lockfile, or explicitly selecting a trusted package index. Consequently, the package artifact is determined by the user's active pip configuration and the state of the configured repository at installation time.The executable imports this package in
scripts/bird_info_skill.pyand refuses to run from its command-line entry point when it is unavailable, even thoughhttp_fetch()contains a standard-libraryurllibfallback. This behavior encourages users to follow the unsafe installation instruction.An unpinned dependency is not inherently malicious, but this installation pattern weakens supply-chain integrity. Exploitation requires compromise or malicious control of a configured package source, a compromised upstream release, or another mechanism capable of supplying an attacker-controlled artifact under the expected package name.
Attack Path
- An attacker compromises the configured Python package source, an upstream package release, or a package mirror selected through the victim's pip configuration.
- The user encounters the documented missing-dependency error.
- The user follows the guide and runs
python3 -m pip install requests. - Pip resolves and installs the attacker-controlled or compromised artifact without a pinned version or required hash.
- Malicious code can execute during package installation or when the skill subsequentl ...[truncated 568 chars]
- Remediation
View remediation
Remediation Suggestions
- Prefer the existing Python standard-library
urllibimplementation and remove the command-line check that makesrequestsmandatory. - If
requestsremains required, pin it to a reviewed exact version in a dependency or lock file. - Require cryptographic hashes, such as through a hash-locked requirements file and
pip install --require-hashes. - Install only from an explicitly trusted HTTPS package index rather than relying on ambient pip configuration.
- Review and update the lockfile through a controlled dependency-management process.
- Avoid installing packages with elevated privileges and use an isolated virtual environment with minimal permissions.
- Keep the declared skill requirements synchronized with the executable dependency requirements.
- Prefer the existing Python standard-library