T08 · Insecure Dependencies
- Location
requirements.txt:1- Finding
Unbounded Third-Party Dependency Versions Create Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
requirements.txt:1-2
Vulnerability Type: Unpinned third-party dependencies
Risk Level: MediumVulnerable Code
text tqsdk>=3.0.0 pandas>=1.3.0Technical Analysis
Both dependencies use open-ended minimum-version constraints. No lockfile or cryptographic package hashes are present in the audited project. Consequently, separate installations may resolve to different and potentially unreviewed future releases.
Python packages can execute code during installation and when imported. This project imports
tqsdkat module initialization, so a compromised release selected by the package resolver could execute with the privileges and environment of the Skill process. This concern is particularly significant because that environment contains theTQ_USERNAMEandTQ_PASSWORDcredentials used by the Skill.This finding does not establish that the currently available
tqsdkorpandasreleases are malicious. It identifies an avoidable supply-chain exposure caused by allowing automatically selected future versions without integrity verification.Attack Path
- An attacker compromises the publishing account, build pipeline, or distribution channel of one of the permitted dependencies.
- The attacker publishes a malicious version satisfying
tqsdk>=3.0.0orpandas>=1.3.0. - A new installation or deployment resolves and downloads that version because no exact version or hash is enforced.
- Attacker-controlled code runs during package installation or subsequent import.
- The malicious code operates under the Skill process identity and may access its environment variables, files, network connectivity, and other resources available to that process.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the account or container installing or running the Skill. The accessible scope may in ...[truncated 232 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace open-ended constraints with exact, reviewed versions, for example:
text tqsdk==<reviewed-version> pandas==<reviewed-version> - Generate and commit a reproducible lockfile through a tool such as
pip-tools, Poetry, or uv. - Require cryptographic hashes for all direct and transitive packages, such as with
pip install --require-hashes. - Retrieve packages only from an explicitly configured trusted registry or an internally controlled package mirror.
- Use automated dependency vulnerability and provenance scanning, while applying upgrades only after review and testing.
- Install and execute the Skill in a least-privileged, isolated environment with restricted filesystem and network access.
- Expose the TQ credentials only to the runtime process that requires them and rotate them if dependency compromise is suspected.
- Replace open-ended constraints with exact, reviewed versions, for example:
