Container Running as Root - Missing USER

HIGH

Dockerfile does not specify USER instruction. Container will run as root by default, which increases the attack surface if the container is compromised.

Rule Information

Language
Docker
Category
Security
Author
Code Pathfinder
Last Updated
2026-01-17
Tags
dockerdockerfilecontainersecurityprivilege-escalationrootuserbest-practicehardeningprinciple-of-least-privilege
CWE References
CWE-250

Interactive Playground

Experiment with the vulnerable code and security rule below. Edit the code to see how the rule detects different vulnerability patterns.

pathfinder ci --ruleset docker/DOCKER-SEC-001 --project .
Vulnerable Code
1
2
3
4
5
6
Security Rule

Similar Rules

Explore related security rules for Docker

MEDIUM

Sudo Usage in Dockerfile

Dockerfile uses 'sudo' in RUN instructions. This is unnecessary during

CRITICAL

Docker Socket Mounted as Volume

Dockerfile mounts Docker socket. This gives the container full control over the host Docker daemon, equivalent to root access.

CRITICAL

Secret in Build Argument

Build argument name suggests it contains a secret. ARG values are visible in image history via 'docker history'.

Frequently Asked Questions

Common questions about Container Running as Root - Missing USER

Dockerfile does not specify USER instruction. Container will run as root by default, which increases the attack surface if the container is compromised.
This vulnerability is rated as HIGH severity, which means it should be addressed promptly as it poses significant security risks that could lead to unauthorized access, data leaks, or system compromise.

Use Code Pathfinder to scan your Docker codebase and automatically detect instances of this vulnerability pattern. Install Code Pathfinder and run the following command in your project directory:

pathfinder ci --ruleset docker/DOCKER-SEC-001 --project .

This rule is aligned with industry-standard security frameworks and classifications:

  • CWE (Common Weakness Enumeration): CWE-250
  • Tags: docker, dockerfile, container, security, privilege-escalation, root, user, best-practice, hardening, principle-of-least-privilege
Yes! Code Pathfinder allows you to customize rules to match your specific security requirements and coding standards. You can modify the detection patterns, adjust severity levels, add custom sanitizers, and configure the rule to fit your organization's security policies. The interactive playground above lets you experiment with the rule and see how it behaves with different code patterns.
When this vulnerability is detected in your code, review the flagged instances carefully. Check the "Vulnerable Code" section above for examples of insecure patterns and the "Security Rule" section to understand what the rule is looking for. Follow security best practices for Docker and consult the CWE/CVE references for detailed remediation guidance. Always test your fixes thoroughly before deploying to production.
Back to SecurityAll Languages →