T08 · Insecure Dependencies
- Location
SKILL.md:9- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 9-12
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: Mediumtext The recommended way is installation through pip. Simply run:bash pip install seisbenchTechnical Analysis
The installation instruction retrieves the latest package version and its transitive dependencies from the package index without enforcing reviewed versions or cryptographic hashes. Consequently, the installed artifacts can change after this Skill has been audited.
If the package, one of its dependencies, or the configured Python package index is compromised, a malicious artifact could execute code during installation or when the package is imported. The instruction does not recommend a lockfile, hash verification, an isolated environment, or validation of the package source.
Attack Path
- An attacker compromises a future
seisbenchrelease, one of its transitive dependencies, or a package index trusted by the victim's pip configuration. - A user or agent follows the Skill and runs
pip install seisbench. - Because no version or hash is specified, pip resolves and downloads the attacker-controlled artifact.
- Malicious code executes during package installation or subsequent import and use.
- The code operates with the permissions of the account running pip or the resulting Python process.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the installing user. Depending on those privileges and the environment, the attacker could read or modify accessible files, steal environment variables or credentials, alter the Python environment, tamper with model outputs, or establish additional persistence. The scope is generally limited to resources available to the pip or Python process, but it may be broader if installation is performed by a privileged account.
- An attacker compromises a future
- Remediation
View remediation
Remediation Suggestions
- Pin
seisbenchto a reviewed, explicitly tested version rather than installing the latest mutable release. - Maintain a lockfile that constrains all transitive dependency versions.
- Require cryptographic hashes, such as with
pip install --require-hashes -r requirements.txt, to verify downloaded artifacts. - Confirm and document the official package name and trusted package index.
- Recommend installation inside a dedicated virtual environment or container under a non-privileged account.
- Establish a dependency update process that includes provenance checks, vulnerability scanning, and review before changing pinned versions.
- Pin
