T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:29- Finding
Execution of Mutable Remote Code and Unverified Dependencies
- Content
View full analysis
- Remediation
View remediation
``` 3. Verify the checked-out commit or release artifact using a trusted signature or an out-of-band cryptographic digest. 4. Replace unconstrained dependencies with a lockfile containing exact versions and package hashes. Install with hash verification, for example: ```bash python -m pip install --require-hashes -r requirements.lock ``` 5. Review direct, Git-based, URL-based, editable, and transitive dependencies before installation. Avoid packages from untrusted indexes. 6. Use an isolated virtual environment or disposable container and run the application as a dedicated, non-root user. 7. Restrict filesystem access, mounted secrets, environment variables, and outbound network connectivity to the minimum required. 8. Add automated dependency vulnerability scanning, provenance verification, and reproducible-build checks to the release process. 9. Document the exact reviewed source revision and dependency-lock digest in `SKILL.md` so users can verify that they are executing the audited version. ]]>
