gitlab-ci-ai-supply-chain-v2
6 rules · Keryn Software Licence · rules 0.8.0 · all packs
How to read a rule
- Severity
- How bad the finding is if it is real:
errorfails a default gate,warningandinfodo not. - Confidence
- P0 exploitable as written; P1 dangerous in context; P2 a heuristic or a posture check: confirm by reading the code.
- False-positive risk
- low: an exact API or flag, so hits are almost always real; medium: the pattern is legitimate in many programs, so check each hit; high: it finds a lead to confirm, so expect benign hits.
- Edge
- The relationship the finding sits on. reaches: content or traffic gets to a thing; calls: one thing invokes another; reads: one thing reads from another; writes: one thing writes to another; sends: data leaves for another party; grants: authority is given or left unchecked; depends_on: something relies on a component it does not verify; trusts: one party believes another without evidence. The boundary it crosses, when there is one: user->prompt (untrusted input reaching a prompt); model->code (model output reaching code, a shell, a query or a page); secret->outside (a secret leaving the trusted side); supply-chain (code, models or prompts pulled in from outside).
- Taxonomy chips
- References for readers who work in OWASP LLM 2025, OWASP Agentic, CWE or NIST AI RMF. They say where a rule belongs, not that a framework is satisfied.
seceng.gitlab.ai-job-secrets-to-llm-or-log
Section titled “seceng.gitlab.ai-job-secrets-to-llm-or-log”warning javascript, typescript, python gitlab-ci
GitLab CI token/secret appears near LLM prompt, messages, provider call, or logging.
Confidence P2: a heuristic or a posture check: confirm by reading the code. False-positive risk medium: the pattern is legitimate in many programs, so check each hit.
Edge inspected: reads one thing reads from another.
CWE-532 CWE-798 LLM02 LLM03 ASI03 ASI04
seceng.gitlab-ci-user-input-to-shell-or-ai
Section titled “seceng.gitlab-ci-user-input-to-shell-or-ai”warning generic gitlab-ci
GitLab CI variable, trigger variable, or pipeline input appears to flow into shell or AI prompt without validation.
Confidence P1: dangerous in context. False-positive risk high: it finds a lead to confirm, so expect benign hits.
Edge inspected: reaches content or traffic gets to a thing.
CWE-20 CWE-78 LLM01 LLM06 ASI05 ASI01 ASI02
seceng.gitlab-ai-generated-commit-no-approval
Section titled “seceng.gitlab-ai-generated-commit-no-approval”info generic gitlab-ci
GitLab CI job appears to commit or push AI-generated changes without a visible manual approval gate.
Confidence P1: dangerous in context. False-positive risk high: it finds a lead to confirm, so expect benign hits.
Edge inspected: grants authority is given or left unchecked.
CWE-862 LLM06 LLM09 ASI02 ASI09
seceng.gitlab-model-download-no-integrity
Section titled “seceng.gitlab-model-download-no-integrity”info generic gitlab-ci
GitLab CI downloads AI model, weights, checkpoint, or artifact without visible checksum/signature verification.
Confidence P1: dangerous in context. False-positive risk high: it finds a lead to confirm, so expect benign hits.
Edge inspected: depends_on something relies on a component it does not verify; it crosses the supply-chain boundary (code, models or prompts pulled in from outside).
seceng.gitlab-runner-docker-privileged-ai-job
Section titled “seceng.gitlab-runner-docker-privileged-ai-job”warning generic gitlab-ci, containers
AI/agent GitLab CI job uses privileged Docker runner or docker socket. This increases blast radius for generated code or tools.
Confidence P1: dangerous in context. False-positive risk high: it finds a lead to confirm, so expect benign hits.
Edge inspected: grants authority is given or left unchecked.
CWE-250 LLM06 LLM03 ASI05 ASI03
seceng.gitlab-unpinned-ai-container-image
Section titled “seceng.gitlab-unpinned-ai-container-image”warning generic gitlab-ci, containers
GitLab CI AI/ML job uses container image without digest pinning.
Confidence P1: dangerous in context. False-positive risk medium: the pattern is legitimate in many programs, so check each hit.
Edge inspected: depends_on something relies on a component it does not verify; it crosses the supply-chain boundary (code, models or prompts pulled in from outside).