T08 · Insecure Dependencies
- Location
SKILL.md:184- Finding
Unpinned VCS Dependency Can Execute Mutable Upstream Code
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 184-187
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code:
bash pip install -e . # from this repo # or pip install git+https://github.com/PatzEdi/dadascribe-api-python.gitTechnical Analysis
The Skill recommends installing a Python package directly from a mutable GitHub repository reference. The command does not specify an immutable commit hash, signed release, version tag, or integrity hash. Consequently, the code installed by the same documented command can change after the Skill has been reviewed.
Installing a Python project with
pipmay execute attacker-controlled build-system or installation code. If the upstream repository, maintainer account, release process, or referenced default branch is compromised, following this instruction could execute arbitrary code under the account running the agent.The alternative local command is also inconsistent with the audited artifact: the project contains only
SKILL.md, not the claimeddadascribepackage. This increases the likelihood that a user or agent will rely on the unaudited remote installation command.Attack Path
- An attacker compromises the upstream GitHub repository, a maintainer account, or the repository's default branch.
- The attacker adds malicious package build or installation logic.
- The Skill or an operator executes:
pip install git+https://github.com/PatzEdi/dadascribe-api-python.git. pipretrieves the current attacker-controlled repository contents.- Malicious build or package code executes with the privileges of the user running
pip. - The payload can access files, environment variables, network resources, and credentials available to that account.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the agent or user ...[truncated 310 chars]
- Remediation
View remediation
Remediation Suggestions
- Prefer the documented HTTPS API and avoid installing executable third-party code when it is unnecessary for transcription.
- If the wrapper is required, use an immutable, reviewed commit hash rather than a mutable branch:
pip install git+https://github.com/PatzEdi/dadascribe-api-python.git@COMMIT_HASH. - Prefer a trusted package registry release with an exact version and verified distribution hashes.
- Maintain a lock file or constraints file containing approved versions and hashes.
- Verify release signatures or attestations where available.
- Install dependencies in an isolated virtual environment or restricted container without administrative privileges.
- Remove or correct the claim that the wrapper is present in the same repository unless the reviewed package is actually included.
