T05 · Unauthorized Access and Privilege Escalation
Warning
- Location
SKILL.md:839- Finding
Unrestricted Environment Variable Enumeration in Kubernetes Workloads
- Content
View full analysis
-- /bin/sh` — exec into container for live debugging: check env vars (`env`), DNS resolution (`nslookup`), network connectivity (`nc -zv`), disk space (`df -h`), memory (`free -m`). ``` ### Technical Analysis The troubleshooting guidance recommends executing a shell inside a Kubernetes container and running `env`. This command enumerates every environment variable available to the workload rather than checking only the configuration relevant to the incident. Container environment variables can contain database passwords, API tokens, cloud credentials, signing secrets, internal service addresses, or other sensitive configuration. Although the Skill does not direct the Agent to transmit these values to an external endpoint, unrestricted enumeration can place secrets in terminal output, Agent context, conversation history, diagnostic records, or copied incident reports. This behavior exceeds minimum privilege when troubleshooting requires only confirmation that a particular configuration variable is present or correctly set. The guidance provides no requirement for user authorization, targeted variable selection, value redaction, or protection against secret disclosure. ### Attack Path 1. A production troubleshooting request activates the DevOps Troubleshooter guidance. 2. The Agent or operator uses Kubernetes permissions that allow `kubectl exec` against an affected pod. 3. Following the Skill instructions, the Agent opens a shell and executes `env`. 4. The container returns all environment variables, including any credentials injected into the workload. 5. The sensitive values enter the Agent's context or terminal history. 6. The values may then be inadvertently included in diagnostic output, incident re ...[truncated 975 chars]- Remediation
View remediation