T08 · Insecure Dependencies
- Location
requirements.txt:1- Finding
Unpinned Third-Party Dependency
- Content
View full analysis
Vulnerability Details
File Location:
requirements.txt:1-2
Vulnerability Type: Unpinned third-party dependencies
Risk Level: MediumVulnerable Code
text dataclasses rdkitTechnical Analysis
The project declares third-party dependencies without exact versions or verified integrity hashes. Consequently, separate installations may resolve to different package releases without any corresponding repository review. This prevents reproducible builds and exposes installation to upstream package compromise, unexpected releases, or dependency-resolution changes.
The
dataclassesdependency is also unnecessary for the documented Python 3.10+ baseline becausedataclassesis included in the Python standard library. Retaining an unnecessary external package increases the supply-chain attack surface.The audit found no evidence that either currently declared package is malicious. The vulnerability is the unconstrained and unverifiable dependency-resolution process.
Attack Path
- A user or deployment system runs a package installation command using
requirements.txt. - The package resolver selects the package versions available from the configured registry at installation time.
- If an upstream account, release, registry, or resolution path has been compromised, the resolver downloads the affected artifact.
- Malicious installation or import-time code executes with the privileges of the user or service performing the installation.
- Because the project specifies neither trusted hashes nor reviewed versions, the installation process does not detect that the resolved artifact differs from the dependency version previously reviewed.
Impact Assessment
Successful exploitation could execute arbitrary code with the privileges of the account installing or running the Skill. Depending on its environment, this may permit access to project files, process environment variables, user-readable credentials, generated ADME results, and ...[truncated 321 chars]
- A user or deployment system runs a package installation command using
- Remediation
View remediation
Remediation Suggestions
- Remove
dataclassesfor the documented Python 3.10+ runtime because it is provided by the standard library. - Pin RDKit to an explicitly reviewed version:
text rdkit==<reviewed-version> - Generate and commit a lock file containing hashes for all direct and transitive dependencies.
- Enforce hash verification during installation, such as with
pip install --require-hashes. - Install only from an approved package index over authenticated TLS, and disable untrusted extra indexes.
- Use automated dependency scanning and a controlled update process to review new releases before changing the lock file.
- Build and run the Skill in a least-privileged, isolated environment with access only to necessary input and output paths.
- Remove
