Privileged Port Exposed

MEDIUM

Exposing port below 1024 typically requires root privileges to bind. Consider using non-privileged ports (>1024) with port mapping or granting CAP_NET_BIND_SERVICE capability.

Rule Information

Language
Docker
Category
Audit
Author
Code Pathfinder
Last Updated
2026-01-17
Tags
dockerdockerfileportexposeprivilegedrootsecurityunixnetworkingcapabilitiesbest-practice
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-AUD-003 --project .
Vulnerable Code
1
2
3
4
5
6
7
8
9
10
Security Rule

Similar Rules

Explore related security rules for Docker

LOW

Dockerfile Source Not Pinned

FROM instruction without digest pinning. Consider using @sha256:... for immutable builds.

Frequently Asked Questions

Common questions about Privileged Port Exposed

Exposing port below 1024 typically requires root privileges to bind. Consider using non-privileged ports (>1024) with port mapping or granting CAP_NET_BIND_SERVICE capability.
This vulnerability is rated as MEDIUM severity, which means it should be reviewed and fixed in a timely manner as it represents a moderate security risk that could be exploited under certain conditions.

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-AUD-003 --project .

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

  • CWE (Common Weakness Enumeration): CWE-250
  • Tags: docker, dockerfile, port, expose, privileged, root, security, unix, networking, capabilities, best-practice
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 AuditAll Languages →