Privileged Port Exposed

medium

Exposes privileged port (<1024) which requires root to bind, conflicting with non-root container best practice

Rule Information

Language
Docker
Category
Audit
Author
Code Pathfinder Team
Last Updated
2024-12-10
Tags
dockerportssecurity

Interactive Playground

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

pathfinder scan --rule cpf/docker-priv-port
Vulnerable Code
Security Rule

Similar Rules

Explore related security rules for Docker

high

Container Running as Root

Detects Dockerfiles without USER instruction, causing containers to run with root privileges

critical

Secret in Build Argument

Detects ARG instructions with names suggesting secrets. Build args are visible in image history

critical

Docker Socket Mounted as Volume

Detects Docker socket mount which gives container full control over host Docker daemon

Frequently Asked Questions

Common questions about Privileged Port Exposed

Exposes privileged port (<1024) which requires root to bind, conflicting with non-root container best practice
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 scan --rule cpf/docker-priv-port

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

  • Tags: docker, ports, security
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 →
Privileged Port Exposed - Docker Security Rule | Code Pathfinder | Code Pathfinder