T08 · Insecure Dependencies
- Location
skill.md:10- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
skill.md, lines 10-12 and 18-20
Vulnerability Type: Unpinned and unverified third-party dependency
Risk Level: MediumVulnerable Code
yaml package: meet-cli bins: - meetbash pip install meet-cliTechnical Analysis
The Skill installs
meet-clifrom the configured Python package index without specifying an exact version, verifying a cryptographic hash, or constraining the package source to a reviewed artifact. Consequently, the code installed when the Skill is activated can change independently of the reviewed project.Python package installation may execute package-controlled build or installation logic. If the package distribution, maintainer account, package index, or dependency chain is compromised, malicious code could run during installation or when the
meetcommand is invoked. The project contains no vendored implementation, lockfile, integrity metadata, or trusted-source declaration that would allow the installed code to be verified against a reviewed version.This finding does not establish that the current
meet-clipackage is malicious. The vulnerability is the absence of version and integrity controls around executable third-party code.Attack Path
- An attacker compromises the package publisher, package index, release process, or a transitive dependency used by
meet-cli. - The attacker publishes a malicious or backdoored release under the package name expected by the Skill.
- The Skill is installed or activated after that release becomes available.
pip install meet-cliresolves and downloads the attacker-controlled release because no exact version or hash is required.- Package-controlled code executes during installation or when the Agent invokes the installed
meetbinary. - The malicious code operates with the privileges and filesystem or network access of the user running the Agent.
Impac
...[truncated 599 chars]
- An attacker compromises the package publisher, package index, release process, or a transitive dependency used by
- Remediation
View remediation
Remediation Suggestions
- Pin
meet-clito an exact version that has been independently reviewed, rather than allowing pip to select the latest available release. - Require cryptographic hashes for the package and all transitive dependencies, such as through a hash-locked requirements file installed with
pip install --require-hashes. - Generate and retain a lockfile or constraints file so dependency resolution is reproducible.
- Document and enforce the trusted package index or verified official distribution source. Disable unintended fallback indexes to reduce dependency-confusion exposure.
- Verify package provenance and release signatures where supported, and periodically review the pinned artifact and its dependency tree.
- Install the CLI in an isolated virtual environment or sandbox under a non-privileged account.
- Restrict the installed process to only the filesystem paths and network destinations required for Meet operations.
- Update the installation example to reference the reviewed version and integrity-controlled installation process instead of
pip install meet-cli.
- Pin
