T08 · Insecure Dependencies
- Location
references/clone.md:26- Finding
Unpinned Remote Repository and Unverified Bundled Binary Execution
- Content
View full analysis
- Remediation
View remediation
test "$(git rev-parse HEAD)" = "" ``` 3. Verify signed tags or commits against an explicitly trusted maintainer key. 4. Publish and verify SHA-256 checksums and signatures for `frpc.exe` and `frpc-linux` before execution. 5. Prefer installing `frpc` from a trusted, version-pinned package source or building it reproducibly from a reviewed upstream release. 6. Pin all Python dependencies with hashes in a lock file. Review direct and transitive dependencies before installation. 7. Avoid editable installation for production use. Build a reviewed wheel in an isolated environment and install the verified artifact. 8. Run installation and startup under a dedicated, unprivileged account or a sandboxed container with minimal filesystem and network access. 9. Do not mount privileged Docker sockets or unrelated host directories into the service environment. 10. Restrict `.env.local` and `frpc-visitor.ini` permissions to the service account and ensure they are excluded from version control and logs. 11. Grant the configured database account only the minimum read or write permissions required for dashboard generation. 12. Restrict tunnel destinations and outbound network access to explicitly required hosts and ports. 13. Bind the FastAPI service to `127.0.0.1` by default unless remote exposure is explicitly required and protected by authentication, TLS, and firewall rules. 14. Add a mandatory integrity-verification step before `pip install`, `python main.py`, or automatic tunnel startup. ]]>
