# Inclusion of Functionality from Untrusted Control Sphere (CWE-829)

The product imports, requires, or includes executable functionality from a source that is outside of the intended control sphere.

**Stack:** Kubernetes

- Prevalence: High Frequently exploited
- Impact: High 3 high-severity rules
- Prevention: Documented 4 fix examples

**OWASP:** Vulnerable and Outdated Components (A06:2021-Vulnerable and Outdated Components) - #6

## Description

When software includes functionality from untrusted sources (such as third-party scripts, external modules, or code from untrusted URLs), attackers can inject malicious code that will be executed with the same privileges as the application.

## Prevention

Prevention strategies for Inclusion of Untrusted Functionality based on 1 Shoulder detection rules.

### Kubernetes

Pin container images to specific version tags or SHA digests for reproducible deployments

## Warning Signs

- [MEDIUM] Container image uses 'latest' tag or no tag.
- [MEDIUM] container images using 'latest' tag or no tag

## Consequences

- Execute Unauthorized Code
- Read Application Data
- Modify Application Data

## Mitigations

- Only include code from trusted, verified sources
- Use Subresource Integrity (SRI) for external scripts
- Implement Content Security Policy (CSP) to restrict sources of executable code

## Detection

- Total rules: 4
- Languages: go, javascript, typescript, yaml, python

## Rules by Language

### Yaml (1 rules)

- **Container Using Latest Tag** [MEDIUM]: Detects container images using 'latest' tag or no tag.
  - Remediation: Use specific image tags for production.

```yaml
containers:
  - name: app
    image: nginx:1.21.6-alpine
```

Learn more: https://shoulder.dev/learn/kubernetes/cwe-829/image-latest-tag