SELinux Separation Disabled

medium

Service explicitly disables SELinux which provides mandatory access control limiting container compromise impact

Rule Information

Language
Docker Compose
Category
Container Security
Author
Code Pathfinder Team
Last Updated
2024-12-10
Tags
docker-composesecurityselinux
CWE References
CWE-732

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/compose-selinux
Vulnerable Code
Security Rule

Similar Rules

Explore related security rules for Docker Compose

critical

Privileged Container Service

Detects services running with privileged mode which disables container isolation

critical

Docker Socket Exposed to Container

Service mounts Docker socket providing unrestricted root access to host

high

Host Network Mode

Service uses host network mode bypassing Docker network isolation

Frequently Asked Questions

Common questions about SELinux Separation Disabled

Service explicitly disables SELinux which provides mandatory access control limiting container compromise impact
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 Compose 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/compose-selinux

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

  • CWE (Common Weakness Enumeration): CWE-732
  • Tags: docker-compose, security, selinux
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 Compose and consult the CWE/CVE references for detailed remediation guidance. Always test your fixes thoroughly before deploying to production.
Back to Container SecurityAll Languages →
SELinux Separation Disabled - Docker Compose Security Rule | Code Pathfinder | Code Pathfinder