T08 · Insecure Dependencies
- Location
SKILL.md:27- Finding
Mutable Third-Party Container Image Is Executed Without Version or Digest Pinning
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it says, but its setup asks users to run an unpinned third-party Docker ASR service that may expose a local transcription endpoint more broadly than intended.
Install only if you are comfortable running a third-party Whisper ASR container. Prefer a pinned image digest, bind the port to 127.0.0.1, add network/resource controls, and avoid sensitive recordings unless you have verified the container and its logging behavior.
SKILL.md:27Mutable Third-Party Container Image Is Executed Without Version or Digest Pinning
SKILL.md:27Unauthenticated ASR Service May Be Published on All Host Network Interfaces
The description is broad enough to trigger on many generic audio or video transcription requests, which can cause the skill to be invoked in contexts the user did not clearly intend. In this skill, broad matching increases the chance that sensitive local media is routed into the workflow and then posted to the ASR HTTP endpoint without sufficient user awareness.
The examples show uploading local files via curl to http://localhost:PORT/asr but do not warn that the full contents of local audio or video are being transmitted to a network service. Even though the endpoint is localhost, it is still an HTTP service boundary; users may not realize sensitive recordings are being sent to a containerized service that could log, retain, or expose data.
The Docker command relies on the image tag :latest, which is mutable and can change over time without review. This creates supply-chain risk because future pulls may run different or compromised code than originally tested, especially for a service that processes user-provided media files.
No suspicious patterns detected.