# Uncontrolled Resource Consumption (CWE-400)

The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.

**Stack:** Kubernetes

- Prevalence: High Frequently exploited
- Impact: Medium Review recommended
- Prevention: Documented 8 fix examples

**OWASP:** Security Misconfiguration (A05:2021-Security Misconfiguration) - #5

## Description

Limited resources include memory, file system storage, database connection pool entries, and CPU. If an attacker can trigger the allocation of these limited resources, but the number or size of the resources is not controlled, then the attacker could cause a denial of service.

## Prevention

Prevention strategies for Resource Exhaustion based on 1 Shoulder detection rules.

### Kubernetes

Define CPU and memory resource limits to prevent resource exhaustion and denial of service

## Warning Signs

- [MEDIUM] Container is missing resource limits.
- [MEDIUM] containers missing resource limits

## Consequences

- DoS: Resource Consumption
- DoS: Crash/Exit/Restart

## Mitigations

- Implement rate limiting
- Use resource quotas
- Implement timeouts for operations

## Detection

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

## Rules by Language

### Yaml (1 rules)

- **Missing Resource Limits** [MEDIUM]: Detects containers missing resource limits.
  - Remediation: Define resource limits for containers.

```yaml
resources:
  limits:
    memory: "256Mi"
    cpu: "500m"
```

Learn more: https://shoulder.dev/learn/kubernetes/cwe-400/missing-resource-limits