T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Unpinned Tencent Cloud SDK Dependency
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it claims, but its credential handling and unsafe TLS troubleshooting guidance are risky enough to warrant review before use.
Use this only with Tencent credentials scoped to the minimum required API access. Avoid submitting confidential media or internal URLs unless your policy permits Tencent Cloud processing. Do not disable TLS verification, do not print any part of SecretKey, prefer per-session or secret-manager injection over persistent user environment variables, and install the SDK in an isolated environment with a pinned version.
SKILL.md:25Unpinned Tencent Cloud SDK Dependency
SKILL.md:61Tencent SecretKey Prefix Exposed in Console Output
SKILL.md:209Documentation Recommends Disabling TLS Certificate and Hostname Verification
scripts/generate.py:253Remote Job Identifier Used as an Unsanitized Output Path Component
Without declared permissions the skill's intent is opaque and cannot be validated.
The skill accepts public URLs and local media files for processing by a third-party cloud service but does not clearly warn users that those inputs will be transmitted to Tencent Cloud. This can lead to unintended disclosure of sensitive images, videos, or internal URLs, especially because local files are base64-encoded and uploaded.
The documentation instructs users to store long-lived cloud credentials in environment variables and even print portions of them during verification, but it lacks strong secret-handling guidance. This increases the risk of credential exposure through shell history, screenshots, logs, shared terminals, or overly broad user-level persistence.
The documentation explicitly recommends disabling SSL certificate validation and hostname verification when downloading generated videos. That enables man-in-the-middle interception or content tampering, allowing an attacker on the network path to substitute malicious or altered files while the client believes they came from Tencent Cloud.
This code accesses sensitive credentials via TENCENT_SECRET_ID and TENCENT_SECRET_KEY. Although the docstring explains how to set them, it does not disclose that the script will consume these secrets at runtime or provide a clear warning about handling credentialed API access.
The script downloads a URL returned by a remote API and writes the response directly to a local file without validating the destination content type, size, or trust boundary of the URL. In this skill context, the file path is fixed under the output directory, so arbitrary path overwrite is not present, but a compromised or unexpected upstream service could cause users to fetch untrusted content, very large files, or internal-network targets if non-public URLs are returned.