T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Unpinned and Unverifiable Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 18-27
Vulnerability Type:T08: Insecure Dependencies
Risk Level: Mediummarkdown ## Setup If Piper is not installed, run the setup script: ```bash scripts/setup-piper.shThis installs
piper-ttsvia pip and downloads a default voice (en_US-kusal-medium).text ### Technical Analysis The Skill instructs users to execute `scripts/setup-piper.sh`, which purportedly installs the `piper-tts` Python package and downloads a voice model. However, that script is absent from the audited project, whose only file is `SKILL.md`. Consequently, its package source, version constraints, download URLs, shell commands, and integrity-validation behavior cannot be reviewed. The documentation does not specify an exact dependency version, package hash, model version, checksum, or signature. Installing a mutable package release and downloading unverified model content creates a supply-chain exposure: the retrieved artifacts can differ from those intended or previously reviewed. The missing script also makes the documented setup process unverifiable and could cause an operator or agent to execute a same-named script obtained from an unintended location. This finding does not establish that `piper-tts` or the referenced voice model is malicious. The risk arises from the undocumented, unpinned, and unverifiable installation process. ### Attack Path 1. A user or agent loads the Skill and follows its setup instructions. 2. The environment supplies the missing `scripts/setup-piper.sh` from another source, or a later package revision adds it without equivalent review. 3. The script installs the current package release and downloads model content without documented version or integrity controls. 4. A compromised package release, substituted download, dependency-confusion package, or malicious replacement script is retrieved. 5. Package installation logic or shell ...[truncated 907 chars]- Remediation
View remediation
Remediation Suggestions
- Include
scripts/setup-piper.shandscripts/piper-speak.shin the project so their behavior can be audited. - Pin
piper-ttsand all transitive dependencies to reviewed versions. - Use a lock file or hash-verified installation, such as pip requirements with
--require-hashes. - Pin voice models to immutable revisions and verify a published cryptographic checksum or signature before use.
- Download only from explicitly documented HTTPS endpoints and reject redirects to untrusted origins.
- Avoid
sudo, system-wide package installation, and other privilege elevation; install into an isolated virtual environment under a least-privileged account. - Fail securely if integrity verification fails, and remove incomplete downloads.
- Document every network destination and clarify that external access is required during setup despite operation being local afterward.
- Ensure script paths are resolved relative to a trusted, verified Skill directory rather than the current working directory.
- Include
