s2i-build
Fail
Audited by Snyk on Mar 12, 2026
Risk Level: HIGH
Full Analysis
HIGH W007: Insecure credential handling detected in skill instructions.
- Insecure credential handling detected (high risk: 0.80). The skill instructs the agent to read the Git remote URL from .git/config and then include that exact [git-url] verbatim in BuildConfig and user-facing output, which risks exposing embedded credentials (e.g., https://user:pass@host) even though it doesn't explicitly ask for API keys or tokens.
MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).
- Third-party content exposure detected (high risk: 0.90). The skill reads Git repository info (.git/config), creates BuildConfig that pulls source from arbitrary Git URLs, and streams/analyzes build logs via the kubernetes MCP (pod_logs) as part of its required workflow (see "To detect Git URL", BuildConfig source sections, and "Stream build logs"/"Debug Build"), which exposes the agent to untrusted user-generated third‑party content that can influence decisions and actions.
MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).
- Potentially malicious external URL detected (high risk: 1.00). The skill takes a Git repository URL (the [git-url] inserted into the BuildConfig/Build and detected from .git/config or provided by the user) at runtime and triggers OpenShift S2I builds that fetch and execute that remote source code, so the git repo URL is a runtime external dependency that can execute code on the cluster.
Issues (3)
W007
HIGHInsecure credential handling detected in skill instructions.
W011
MEDIUMThird-party content exposure detected (indirect prompt injection risk).
W012
MEDIUMUnverifiable external dependency detected (runtime URL that controls agent).
Audit Metadata