DKER-EE-002110 - All Docker Enterprise containers must be restricted from acquiring additional privileges.

Information

Restrict the container from acquiring additional privileges via suid or sgid bits.

A process can set the no_new_priv bit in the kernel. It persists across fork, clone, and execve. The no_new_priv bit ensures that the process or its children processes do not gain any additional privileges via suid or sgid bits. This way a lot of dangerous operations become a lot less dangerous because there is no possibility of subverting privileged binaries.

no_new_priv prevents LSMs like SELinux from transitioning to process labels that have access not allowed to the current process.

By default, new privileges are not restricted.

Solution

This fix only applies to the use of Docker Engine - Enterprise on a Linux host operating system.

Start the containers as below:

docker run --rm -it --security-opt=no-new-privileges <image>

A reference for the docker run command can be found at https://docs.docker.com/engine/reference/run/.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Docker_Enterprise_2-x_Linux-Unix_V2R2_STIG.zip

Item Details

Category: CONFIGURATION MANAGEMENT

References: 800-53|CM-7a., CAT|I, CCI|CCI-000381, Rule-ID|SV-235816r960963_rule, STIG-ID|DKER-EE-002110, STIG-Legacy|SV-104805, STIG-Legacy|V-95667, Vuln-ID|V-235816

Plugin: Unix

Control ID: 6f34c338f75cb440ad253d5995e0aed5c022f325951a802d4ddc3345ceb2a40e