T03 · Remote Payload Retrieval and Execution
- Location
scripts/check-render-env.sh:34- Finding
Remote API Responses Are Executed as Python Code
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Render environment checker has a coherent purpose, but its script can expose a Render API key to a user-configured server and can accidentally execute API responses as Python code.
Review or patch the script before installing. It should pin authenticated requests to Render's HTTPS API or strictly allowlist trusted origins, and it should pass API JSON to Python as data through a separate file descriptor or file instead of stdin used for Python source.
scripts/check-render-env.sh:34Remote API Responses Are Executed as Python Code
scripts/check-render-env.sh:20Render API Key Can Be Sent to an Arbitrary Configured Server
The skill explicitly instructs the user to run a shell script and declares required binaries, but it does not declare any tool scope such as permissions or allowed-tools. That means an agent/runtime may execute shell-capable behavior without an explicit least-privilege boundary, increasing the chance of unintended command execution or broader host access than the skill actually needs.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
set -euo pipefail
API_BASE="${RENDER_API_BASE_URL:-https://api.render.com/v1}"
TOKEN="${RENDER_API_KEY:-}"
SERVICE_ID="${RENDER_SERVICE_ID:-}"
SERVICE_NAME="${RENDER_SERVICE_NAME:-}"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
set -euo pipefail
API_BASE="${RENDER_API_BASE_URL:-https://api.render.com/v1}"
TOKEN="${RENDER_API_KEY:-}"
SERVICE_ID="${RENDER_SERVICE_ID:-}"
SERVICE_NAME="${RENDER_SERVICE_NAME:-}"