T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:5
- Finding
- Unpinned Third-Party CLI Executes with Access to Tencent Cloud Credentials## Vulnerability Details **File Location**: `SKILL.md`, lines 5–20 **Vulnerability Type**: `T08: Insecure Dependencies` **Risk Level**: Medium **Vulnerable Code Snippet**: ```yaml metadata: {"requires": {"bin": ["clscli"], "env": ["TENCENTCLOUD_SECRET_ID", "TENCENTCLOUD_SECRET_KEY"]}} ``` ```markdown ## Setup 1. Install clscli (Homebrew): ```bash brew tap dbwang0130/clscli brew install dbwang0130/clscli/clscli ``` 2. Get credentials and region list: https://cloud.tencent.com/document/api/614/56474 3. Set environment variables (same as Tencent Cloud API common parameters): ```bash export TENCENTCLOUD_SECRET_ID="your-secret-id" export TENCENTCLOUD_SECRET_KEY="your-secret-key" ``` ``` ### Technical Analysis The Skill instructs users to install `clscli` from a third-party Homebrew tap without pinning an immutable release, formula revision, source commit, checksum, or cryptographic signature. The project contains only `SKILL.md`; consequently, neither the executable nor its Homebrew formula can be statically verified as part of this audit. The installed executable is subsequently expected to run in an environment containing `TENCENTCLOUD_SECRET_ID` and `TENCENTCLOUD_SECRET_KEY`. Any process running under the same environment can read these variables. If the tap, formula, release artifact, upstream hosting account, or maintainer account is compromised, a modified executable could access and exfiltrate those credentials and any log data returned by Tencent Cloud CLS. This finding does not establish that the current third-party package is malicious. The risk arises from the mutable, unverified supply-chain trust relationship combined with access to cloud credentials. ### Attack Path 1. An attacker compromises the third-party Homebrew tap, formula repository, upstream release artifact, or a maintainer account. 2. The attacker modifies the formula or referenced artifact ...[truncated 1361 chars]
- Remediation
- ## Remediation Suggestions 1. Link to the exact authoritative source repository rather than the generic homepage currently shown in the metadata. 2. Pin installation to an immutable, reviewed release and Homebrew formula commit instead of tracking a mutable tap revision. 3. Publish expected SHA-256 or stronger artifact digests and verify them before installation. 4. Prefer signed release artifacts and document verification of the publisher's cryptographic signature. 5. Review and vendor the Homebrew formula or provide a reproducible build process so users can verify the relationship between source and binary. 6. Use short-lived Tencent Cloud credentials instead of long-lived static keys wherever supported. 7. Assign a dedicated IAM identity with only the minimum read-only CLS permissions required to list topics, query logs, and retrieve context. 8. Restrict credentials to the necessary accounts, regions, logsets, and topics, and rotate them immediately if dependency compromise is suspected. 9. Avoid globally exporting credentials for longer than necessary. Provide credentials only to the intended process through an approved secret-management mechanism. 10. Document the dependency trust model, supported version, required IAM actions, credential rotation procedure, and steps for validating installed binaries.