Invalid Port Number
highEXPOSE instruction contains invalid port number. Valid ports are 1-65535
Rule Information
Language
Docker
Category
Correctness
Author
Code Pathfinder Team
Last Updated
2024-12-10
Tags
dockercorrectness
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-portVulnerable 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 Invalid Port Number
EXPOSE instruction contains invalid port number. Valid ports are 1-65535
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 scan --rule cpf/docker-portThis rule is aligned with industry-standard security frameworks and classifications:
- Tags: docker, correctness
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.