T03 · Remote Payload Retrieval and Execution
Error
- Location
- README.md:79
- Finding
- Unverified Remote Payload Retrieval and Execution<![CDATA[ ## Vulnerability Details **File Location**: `README.md:79-100` **Supporting Locations**: `SKILL.md:8`; `bin/REFERENCE.md:3-15` **Vulnerability Type**: Remote executable bootstrap without documented integrity or provenance verification **Risk Level**: High ### Vulnerable Code Snippets `README.md:79-100`: ```markdown ## Binary Resolution Order `scripts/threadpilot` resolves runtime in this order: 1. `THREADPILOT_BIN` (explicit path) 2. Cached binary in `.threadpilot/bin/` 3. System `threadpilot` from `PATH` 4. Auto-install from `vood/threadpilot` release asset by version 5. Source fallback by cloning `vood/threadpilot` and building Manual install/bootstrap: ```bash scripts/threadpilot install ``` ## Environment Variables - `THREADPILOT_BIN`: Force exact binary path. - `THREADPILOT_CACHE_DIR`: Override local cache directory (default: `.threadpilot`). - `THREADPILOT_RELEASE_BASE_URL`: Release base URL for binary downloads. - `THREADPILOT_VERSION`: Binary release version to download (default: `v0.1.0`). - `THREADPILOT_REPO`: Git repo used for source bootstrap. - `THREADPILOT_REF`: Git ref/branch for source bootstrap (default: `main`). - `THREADPILOT_SOURCE_DIR`: Build from local source tree instead of cloning. ``` `SKILL.md:8`: ```markdown This skill runs the `threadpilot` CLI and can auto-bootstrap it from `github.com/vood/threadpilot`. ``` `bin/REFERENCE.md:3-15`: ```markdown This repository does not store `threadpilot` executables. Runtime binaries are sourced from: - Repository: `https://github.com/vood/threadpilot` - Releases: `https://github.com/vood/threadpilot/releases` - Download pattern: - `https://github.com/vood/threadpilot/releases/download/<version>/threadpilot-<os>-<arch>` Defaults used by `scripts/threadpilot`: - `THREADPILOT_VERSION=v0.1.0` - `THREADPILOT_RELEASE_BASE_URL=https://github.com/vood/threadpilot/releases/download` ``` ### Technical Analysis The documented workflow retrieves and executes a binary from an ...[truncated 2930 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Include the referenced launcher and safety wrappers in the package so their complete behavior can be audited. 2. Pin release artifacts to an immutable version and publish a trusted SHA-256 or stronger digest for every supported operating-system and architecture combination. 3. Verify the expected digest before making a downloaded file executable or launching it, and fail closed on any mismatch. 4. Add cryptographic release-signature verification using a pinned maintainer key or a verifiable keyless signing framework such as Sigstore. 5. Replace the mutable `main` source fallback with a pinned full commit hash. Verify the checked-out commit before building. 6. Disable automatic source fallback by default. Require explicit user approval before downloading, compiling, or executing external code. 7. Treat `THREADPILOT_RELEASE_BASE_URL`, `THREADPILOT_REPO`, `THREADPILOT_REF`, `THREADPILOT_BIN`, and `THREADPILOT_SOURCE_DIR` as security-sensitive inputs. Reject unexpected values in normal operation or require explicit approval for overrides. 8. Do not silently trust a `threadpilot` executable found through `PATH`. Resolve an approved absolute path and verify its digest or signature. 9. Store downloaded artifacts in a user-private directory with restrictive permissions, avoid unsafe symbolic-link handling, and perform atomic installation. 10. Publish a software bill of materials and provenance metadata for the binary and source build. 11. Ensure Reddit credentials and browser profiles are exposed only to the verified process, and avoid forwarding unrelated environment secrets. 12. Correct the package documentation or include the missing `scripts/` and `ops/` files before describing the safety wrappers as production-ready. ]]>