T08 · Insecure Dependencies
- Location
README.md:53- Finding
Unpinned Third-Party Dependencies in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
README.md:53andREADME.md:62
Vulnerability Type: Supply-chain exposure through mutable dependency resolution
Risk Level: MediumVulnerable Code
bash pip install "funasr>=1.4.1" modelscope httpx pyyamlbash pip install inferfabricTechnical Analysis
The documented installation process installs multiple third-party packages without exact version constraints or integrity hashes. The
funasrconstraint accepts any release at or above version 1.4.1, whilemodelscope,httpx,pyyaml, andinferfabrichave no version constraints.Consequently, the effective code installed by users can change after this skill has been reviewed. Package installation can execute package-controlled build hooks, and imported dependencies execute with the privileges of the user running the skill. This creates exposure to compromised package releases, malicious transitive dependencies, unexpected dependency substitutions, and incompatible future versions.
This finding does not establish that any currently named package is malicious. The risk arises from the installation process permitting mutable, unverified dependency resolution.
Attack Path
- An attacker compromises the publishing account, distribution process, or dependency chain of one of the referenced packages.
- The attacker publishes a malicious version that satisfies the unconstrained or lower-bounded requirement.
- A user follows the README installation instructions.
pipresolves and downloads the malicious version because no reviewed lock file, exact version, or hash prevents it.- Attacker-controlled code executes during installation or when the dependency is imported at runtime.
Impact Assessment
Malicious dependency code would generally execute with the operating-system privileges of the user performing the installation or running the ASR skill. Depending on those privilege ...[truncated 305 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every direct dependency to a reviewed exact version rather than using open-ended or lower-bounded constraints.
- Generate and distribute a lock file that includes all transitive dependencies.
- Record cryptographic hashes and install with
pip --require-hashes. - Configure installation to use an explicitly trusted package index and document package provenance.
- Run dependency vulnerability and provenance scanning in CI.
- Test and review dependency upgrades before updating the lock file.
- Recommend installation into an isolated virtual environment under a non-privileged account.
