T08 · Insecure Dependencies
- Location
scripts/configure_clawhub_mirror.sh:7- Finding
Persistent redirection to an insufficiently verified third-party package and API endpoint
- Content
View full analysis
Vulnerability Details
File Location:
scripts/configure_clawhub_mirror.sh:7-21
Vulnerability Type: Supply-chain trust boundary violation
Risk Level: MediumVulnerable Code
bash MIRROR_URL="https://cn.clawhub-mirror.com" BASHRC="$HOME/.bashrc" if grep -q "CLAWHUB_REGISTRY=$MIRROR_URL" "$BASHRC" 2>/dev/null; then echo "ClawHub mirror is already configured" else cat >> "$BASHRC" << EOF # ClawHub mirror configuration export CLAWHUB_REGISTRY=$MIRROR_URL export CLAWHUB_SITE=$MIRROR_URL EOF fiThe same endpoint is also recommended in
SKILL.md:20-28,62andreferences/clawhub-mirror-verification.md:4-13,46.Technical Analysis
The script persistently redirects both ClawHub package retrieval and site/API traffic to
https://cn.clawhub-mirror.com. Although the documentation describes this endpoint as officially recognized, the project provides no independently verifiable ownership information, certificate or public-key pinning, signed repository metadata, package signature validation, or checksum verification.TLS protects traffic in transit but does not establish that packages returned by the selected registry are equivalent to packages from the official source. The mirror therefore becomes a persistent supply-chain trust anchor with influence over package contents, search results, and API responses.
This finding does not establish that the endpoint is currently malicious. The vulnerability is the persistent delegation of package and API trust without integrity controls or documented provenance.
Attack Path
- A user runs the configuration script or follows the Skill instructions.
- The script appends
CLAWHUB_REGISTRYandCLAWHUB_SITEto the user's shell startup file. - Future ClawHub sessions automatically send package and API requests to the configured endpoint.
- The endpoint, its DNS, hosting account, certificate issuance path, or publi ...[truncated 844 chars]
- Remediation
View remediation
Remediation Suggestions
- Use only an endpoint whose ownership and official status can be independently verified.
- Document authoritative provenance, including a link from an official ClawHub-controlled domain.
- Verify signed repository metadata and package signatures before installation.
- If signatures are unavailable, publish trusted checksums through a separate authenticated channel and verify them locally.
- Avoid redirecting
CLAWHUB_SITEunless API redirection is strictly required; package registry and API traffic should have separate trust decisions. - Obtain explicit user confirmation before making the endpoint persistent.
- Back up the original configuration and provide a rollback command that removes only settings added by this script.
- Clearly state that successful
clawhub searchoutput proves connectivity only; it does not establish endpoint ownership or package integrity.
