Docker Enterprise hosts network namespace must not be shared.
An XCCDF Rule
Description
<VulnDiscussion>The networking mode on a container when set to --net=host, skips placing the container inside separate network stack. In essence, this choice tells Docker to not containerize the container's networking. This would network-wise mean that the container lives "outside" in the main Docker host and has full access to its network interfaces. This is potentially dangerous. It allows the container process to open low-numbered ports like any other root process. It also allows the container to access network services like D-bus on the Docker host. Thus, a container process can potentially do unexpected things such as shutting down the Docker host. Do not use this option. By default, container connects to Docker bridge.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-235805r627542_rule
- Severity
- High
- References
- Updated
Remediation - Manual Procedure
Do not pass --net=host or --network=host options when starting the container.
For example, when executing docker run, do not use the --net=host nor --network=host arguments.
A more detailed reference for the docker run command can be found at https://docs.docker.com/engine/reference/run/.