T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unverifiable External Script Executed from a Mutable Absolute Path
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:17-24
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumThe skill depends on an executable located outside the audited project:
text /home/ubuntu/.openclaw/workspace/scripts_gmncode_image.pyIt directs the agent to invoke that external dependency as follows:
bash /home/ubuntu/.openclaw/workspace/scripts_gmncode_image.py <image_path> "your prompt"The same dependency is also documented in
README.md:5-12. The project contains onlySKILL.mdandREADME.md; therefore, the referenced script, its network endpoint, its dependency chain, and its handling of images and credentials could not be audited.Technical Analysis
The skill executes an absolute-path script that is not bundled, version-pinned, or integrity-verified by the audited package. The documented script requires
GMNCODE_API_KEYand is intended to transmit image content to an external Responses API.Because the script exists outside the skill package, its behavior can change independently after this skill has been reviewed. If another user, package, process, or compromised update mechanism can modify the referenced file, legitimate-looking invocations of the skill will execute substituted code.
A substituted script would run with the permissions of the agent process. It could read the supplied image, inspect environment variables inherited by the process, access other files permitted to that account, invoke local commands, or communicate with unauthorized network destinations. The audit found no evidence that the current external script is malicious; the risk arises because its implementation and integrity are outside the reviewed artifact.
Attack Path
- An attacker obtains write access to
/home/ubuntu/.openclaw/workspace/scripts_gmncode_image.pyor controls the mechanism that installs or updates it. - The attacker replaces or modifies the scr ...[truncated 1390 chars]
- An attacker obtains write access to
- Remediation
View remediation
Remediation Suggestions
- Bundle the image-processing script inside the skill package so its implementation is included in security reviews.
- Invoke the bundled script through a package-relative, canonicalized path rather than a mutable workspace-wide absolute path.
- Pin the script and all dependencies to reviewed versions, and verify a cryptographic checksum or signature before execution.
- Restrict ownership and permissions so only a trusted administrator or deployment process can modify the script.
- Document and enforce an allowlist for the exact API hostname, protocol, and destination used to transmit images.
- Pass only the required API credential instead of inheriting the complete parent environment.
- Use a dedicated, least-privileged process with restricted filesystem and network access.
- Obtain explicit user approval before transmitting potentially sensitive images to an external service.
- Review the script for command injection, unsafe subprocess use, insecure temporary files, credential logging, and insufficient TLS validation.
- Add automated integrity checks and fail closed if the script is missing, modified, or resolves outside the expected package directory.
