T08 · Insecure Dependencies
- Location
references/cli-installation-guide.md:24- Finding
Unverified and Unpinned CLI Binary Installation into a Privileged PATH
- Content
View full analysis
- Remediation
View remediation
' "${archive}" | sha256sum --check - ``` 4. Prefer a vendor-signed package or release signature and validate it using a pinned, independently distributed public key. 5. Inspect archive member paths before extraction and extract into a newly created, non-privileged temporary directory. 6. Avoid directly overwriting a system-wide executable. Stage and verify the binary first, then use an operating-system package manager or a controlled administrative deployment process. 7. Pin plugin versions and disable automatic plugin installation by default. Require explicit review before installing or updating a plugin. 8. Record the installed CLI and plugin versions and validated artifact digests in audit logs. 9. Run the CLI with a least-privileged RAM identity so that compromise does not automatically expose full import capabilities. ]]>
